Welcome to the GraphXSource API collection. This API collection enables seamless integration with the Graphxsource system for managing orders and related processes. The key functionalities include:
\nCreate orders: Submit new orders into the Graphxsource system.
\nCheck order status: Retrieve real-time status updates for submitted orders.
\nGet completion details: Access detailed information on orders upon completion.
\nPlace alerts or queries: Add alerts or queries to orders when revisions are required or additional information is needed.
\nCustomer API configuration: Configure customer-specific APIs to:
\nSend notifications on order completion.
\nNotify customers about file availability for download.
\nInform customers when revisions requested on orders are fulfilled by the artist.
\nThese APIs support automation of order workflows, ensure timely communication, and help track order progress efficiently.
\n📄 Description:
\nThis endpoint generates an authentication token that is required for all subsequent API requests. The token is created using the same username and password credentials as used for logging into the Graphxsource system.
\n📄 Functionality:
\nAccepts valid system username and password in the request body.
\nReturns a bearer token upon successful authentication.
\nThe token must be included in the Authorization header of all API requests
This is the sample endpoint where you can test the call using an API token.
\n","urlObject":{"protocol":"https","path":["security","testapiwithtoken"],"host":["core","api","netemb","com"],"query":[],"variable":[]}},"response":[{"id":"6a9b8e19-39ca-4f2f-b9d1-2fc1ea6175ad","name":"2.\tTestAPIWithToken","originalRequest":{"method":"POST","header":[],"url":"https://core.api.netemb.com/security/testapiwithtoken"},"status":"OK","code":200,"_postman_previewlanguage":"plain","header":[{"key":"Content-Type","value":"text/plain; charset=utf-8"},{"key":"Content-Encoding","value":"gzip"},{"key":"Vary","value":"Accept-Encoding"},{"key":"Server","value":"Microsoft-IIS/10.0"},{"key":"X-Powered-By","value":"ASP.NET"},{"key":"Date","value":"Tue, 12 Sep 2023 07:14:26 GMT"},{"key":"Content-Length","value":"123"}],"cookie":[],"responseTime":null,"body":"valid"}],"_postman_id":"91bcc7ed-3bfd-45c1-bb69-79ef27d22343"},{"name":"3.\tTestAPIWithoutToken","id":"cb9557eb-6423-4c32-86a1-0a63e416e813","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"https://core.api.netemb.com/security/testapiwithouttoken","description":"This is the sample endpoint to check the API call without a token. (A read-only API endpoint).
\n","urlObject":{"protocol":"https","path":["security","testapiwithouttoken"],"host":["core","api","netemb","com"],"query":[],"variable":[]}},"response":[{"id":"6f1ce55e-8bde-410d-989c-413536636a2c","name":"3.\tTestAPIWithoutToken","originalRequest":{"method":"POST","header":[],"url":"https://core.api.netemb.com/security/testapiwithouttoken"},"status":"OK","code":200,"_postman_previewlanguage":"plain","header":[{"key":"Content-Type","value":"text/plain; charset=utf-8"},{"key":"Content-Encoding","value":"gzip"},{"key":"Vary","value":"Accept-Encoding"},{"key":"Server","value":"Microsoft-IIS/10.0"},{"key":"X-Powered-By","value":"ASP.NET"},{"key":"Date","value":"Tue, 12 Sep 2023 07:11:22 GMT"},{"key":"Content-Length","value":"123"}],"cookie":[],"responseTime":null,"body":"valid"}],"_postman_id":"cb9557eb-6423-4c32-86a1-0a63e416e813"}],"id":"a670ec48-8715-4d69-adcb-6a543645ede1","_postman_id":"a670ec48-8715-4d69-adcb-6a543645ede1","description":""},{"name":"Get Order Profiles/ Master Data","item":[{"name":"1. Get Embroidery Order Profiles","id":"fe6bed1c-ba74-4b5b-8bc6-6b2de907dc41","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"noauth","isInherited":false},"method":"POST","header":[],"body":{"mode":"raw","raw":"{\r\n \"CustomerUserName\" : \"BrentAlec\" \r\n }","options":{"raw":{"language":"json"}}},"url":"https://core.api.netemb.com/GetEmbroideryTemplatesByCustomerName","description":"📄 Description:
\nThis endpoint provides the Embroidery Template Name and Template ID for the specified customer. The response includes both customer-specific templates and corporate templates.
\n📄 Functionality:
\nReturns a list of embroidery templates linked to the provided customer name.
\nIncludes both customer templates and corporate templates in the result.
\nNo authorization token is required to access this endpoint.
\n📄 Description:
\nThis endpoint provides the Artwork Template Name and Template ID for the specified customer. The response includes both customer-specific templates and corporate templates.
\n📄 Functionality:
\nReturns a list of artwork templates linked to the provided customer name.
\nIncludes both customer templates and corporate templates in the result.
\nNo authorization token is required to access this endpoint.
\n📄 Description:
\nThis endpoint provides the Color Seperation Template Name and Template ID for the specified customer. The response includes both customer-specific templates and corporate templates.
\n📄 Functionality:
\nReturns a list of Color Sep templates linked to the provided customer name.
\nIncludes both customer templates and corporate templates in the result.
\nNo authorization token is required to access this endpoint.
\n📄 Description:
\nThis endpoint provides a list of Master Data IDs that can be used when placing an embroidery order to specify the values for additional parameters.
\n📄 Functionality:
\nReturns IDs and corresponding values for the following parameters:
\nThread Manufacturer
\nEmbroidery Stitch Format
\nStart and Exit Point
\nFabric Type
\nFabric Color
\nOnly a Bearer token is required for authorization.
\n📄 Description:
This endpoint is used to create new embroidery orders or rework embroidery orders in the system.
📄 Functionality:
\n✅ New Orders
\nTo create a new embroidery (EMB) order, the following parameters are required:
\nTemplateID
DesignName
AttachmentBase64 or AttachmentURL
FileName
FileExtension
CustomerUserName
✅ Rework Orders
\nTo create a rework embroidery order, the following parameters are required:
\nCustomerUserName
OriginalOrder
The system will automatically use design information from the specified original invoiced order.
\nRework orders can only be placed against invoiced orders.
\n✅ Promo Code
\nThe optional PromoCode parameter can be used to apply valid promotions.
Possible validation messages if the promo code is invalid:
\nNot a valid Promotion code.
\nEither the promotion code is not enabled or it has expired.
\nThe promotion code is not valid for Embroidery order.
\nThe usage count limit for this website is over. You cannot use this promotion code.
\nThe promotion code supplied is not applicable to your pricing method.
\n✅ Credit Card Validation
\nIf the user’s credit card is expired, the system will not allow the order to be placed.
\nA relevant validation message will be returned in the response.
\n✅ PO Number Requirement
\n✅ Additional Parameters (Master Data IDs)
\nThreadManufacturerIDs, EmbStichFormatID, StartAndExitPointID, FabricColorID: Use valid IDs from the Get Master Field IDs endpoint.
FabricTypeIDs: Up to three IDs can be passed in this parameter.
Users can request a mockup as an add-on within an Embroidery order.
\nWhen this add-on is enabled, product details are mandatory and must be provided in the request payload. These details will be used to generate the mockup using the production-ready embroidery files.
\nKey Notes:
\nMockup generation is supported only when the mockup add-on is set to true.
ProductDetails must be included to ensure accurate mockup creation.
The mockup will be generated based on finalized production files.
\n📄 Description:
The CreateArtworkOrder API is used to create new artwork orders or place rework orders with order type = Artwork/ Creative Art / DTF
📄 Functionality:
\nTo create a new artwork order, the following parameters are required:
\nTemplateID
DesignName
AttachmentBase64 (or AttachmentURL)
FileName
FileExtension
CustomerUserName
⚠ Note:
\nIf the service level type is not set in the template, the API will return a validation error in the response.
\nTo place a rework order, the following parameters are required:
\nCustomerUserName
OriginalOrder
⚠ Important:
\nThe application will always use the design information from the specified OriginalOrder.
A rework order can only be placed against an invoiced original order.
\nYou can apply a valid promotion using the PromoCode parameter.
If the promotion code is invalid, you may receive one of the following validation messages:
\nNot a valid Promotion code.
Either the promotion code is not enabled or it has expired.
The promotion code is not valid for Artwork order.
The usage count limit for this website is over. You cannot use this promotion code.
The promotion code supplied is not applicable to your pricing method.
If the credit card is expired, the API will not allow you to place the order and a relevant validation message will be returned in the response.
\nIf the PO Number is mandatory for the user:
\n📄 Description:
\nThe CreateColorSepOrder API is used to create new orders or place rework orders with order type = Color Sep.
📄 Functionality:
\nTo create a new Color Sep order, the following parameters are required:
\nTemplateID
ProjectName
CustomerUserName
TypeAndColorOfSubstrateToBePrintedOn
✅ Multiple Locations:
\nYou can create a Color Sep order with multiple locations.
\nTemplateID is mandatory for each location.
In case of multiple locations, the Preferred Delivery and Add Ons will be taken from the Order Profile set for location 1.
\nTo place a rework order, the following parameters are required:
\nCustomerUserName
OriginalOrder
LocationNumber
ReworkInstruction
⚠ Important:
\nThe application will always use the design information from the specified OriginalOrder.
A rework order can only be placed against an invoiced original order.
\n📄 Description:
\nThis call provides the current status of an order along with any alert details associated with that order.
\n📄 Functionality:
\nReturns the current status of the specified order.
\nIncludes alert details if any alerts exist for the order.
\nFor orders with Invoiced status:
\nPossible Order Status values:
\nOrder Screening
Additional Info Required
Assigned to Artist
Quality Check
Ready for Delivery
Invoiced
📄 Description:
\nThis API provides the completed files for the specified Order ID.
\n📄 Functionality:
\nReturns a list of completed files for the order, along with the order’s last modified date and time.
\nEach file object in the response includes the following details:
\nA downloadable blob URL
\nThe actual filename
\nThe file extension
\nModifiedDateTime
\nFor embroidery orders, the response also includes:
\nColor information
\nStitch count
\n📄 Description:
\nThis API allows the customer to post an alert on any order.
\n📄 Functionality:
\nEnables customers to submit an alert linked to a specific order.
\nSupports adding attachments to the alert.
\nThe system will update Customer whenever artist will place an alert on their order. The customer needs to provide the endpoint for the updates. Whenever artist will post an alert on the order, the customer will get updated using the endpoint shared by customer.
\n","urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"bb3cadc2-d676-4d2c-94c1-8f11e5b9aa92"},{"name":"2. Update Customer on Order Completion","id":"b7d0065b-446f-470c-b3e0-815fa0b98e5b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\r\n \"OrderReferenceNumber\": null,\r\n \"Message\": \"Order <📄 Description:
\nThe system will notify the customer once an order is completed and the files are ready for download.
\n📄 Functionality:
\nThe system sends an update to the customer-provided endpoint when the order reaches completion.
\nThe update includes relevant order details (e.g., order reference number, completion status, download information).
\nThe customer must provide a valid endpoint URL to receive these notifications.
\n📄 Description:
\nThe system will notify the customer once a revision requested on a completed order has been processed and finalized.
\n📄 Functionality:
\nThe system sends an update to the customer-provided endpoint when the revision is completed.
\nThe update includes details such as the order reference number, revision status, and any completed file information (if applicable).
\nThe customer must provide a valid endpoint URL to receive these revision completion updates.
\nThis folder contains APIs that allow customers to register their callback URLs / webhook endpoints.
\nOur system will send automated notifications to these URLs when key actions occur, such as:
\nOrder completion
\nStaff alert posted on the order
\nRevision request completion
\n⚠️ Note: Customers are responsible for providing and managing these endpoints. Ensure that the URLs are reachable and secured (e.g. HTTPS) to receive timely updates.
\n","_postman_id":"7a9a5972-06e3-44d5-939a-2da7fa364462"}]}