This starts normally within a few minutes. Signals for the step 2 order will be generated when the order is getting processed. Check that the order is accepted by the API and that you can see it in the admin panel. Specify required options, like paper type and total pages. Post a regular book order if you support books. Make sure you have a CloudSignal Webhooks configuration. CloudCore API Interface in Sandbox modeĬheck configurations, make sure you have a CloudCore API Interface with mode set to Sandbox.It ensure that all aspects of the integration are tested in an easy and structured way. The time between attempts will be increase after each attempt.Ĭ has a predefined test checklist we recommend all clients to follow. 100 attempts will be made before giving up. If you didn't receive the signals in the first attempt, the CloudSignal sender service will push the signal again. the order reference and the item reference do not match. Cancel can be used to cancel a signal that your system can not accept e.g.Resend will reset the attempts counter and the state of the signal and the signal sender will pick it up shortly.The HTTP response code from your signal endpoint on the latest delivery attemptĪ textual description of the state the signal is inĭate and time when the signal was createdĭate and time when the signal was delivered successfullyįor each signal you can Cancel or Resend: The number of delivery attempts the system has made The name of the account the signal belongs to You can follow the latest signals in the admin dashboard under "CloudSignal Webhooks" and "Logs" in the menu.Įach of the fields are described here: Field Do a number of these test orders to get more familiar with the Cloudprinter Core API.įor each order that gets processed, a number of signals are generated. You can go to the admin dashboard and see the order as well. When you get a HTTP status code 201 back the order has been created. Check the response of the request, for most errors with HTTP status code 400 an error and info text are returned to help you debug.Is the structure of the JSON valid? A HTTP status code 400 or 500 could be returned here.Raw data in the body? The raw JSON should be in the body of the request, no form-data, binary etc.Content type set to 'application/json'? If not the API will not parse it as JSON.Correct API key? If not a 401 HTTP status is returned.The JSON to post to the Cloudprinter Core API is documented here - Cloudprinter Core APIĪ few of the common issues to check if the order was not accepted: This is all about getting the first order accepted by the API. That is also perfectly fine and makes it easiest for you. We often see that developers start with Postman or cURL to get the first order through. You now have setup all the basic elements needed to post the first Sandbox order. Printer signals are generated to simulate that the order was printed and shipped.Orders are not pushed to any printer, but otherwise processed the same way in the system.Having a CloudCore API Interface in Sandbox mode makes the integration tests easier. The API key provided on the CloudSignal Webhooks must be validated at your signal endpoint.Access limitation can be added on IP level on your endpoint - More information here.A signal endpoint in your system must be exposed to Cloudprinters system.When you create a new webhooks configuration you choose which signal types you want to subscribe on. We already created one for you when you created the account, you just need to get the API key from there.Ĭreate a CloudSignal Webhooks - This is the configuration for the service for sending signals back to your system. Login to the admin dashboard and go to 'CloudCore API Interfaces'. It provides you with a unique API key, which links the order to the specific account. # Table of contentīefore the testing can start a few configurations have to be in place, each described here.Ĭreate a CloudCore API Interface - This is the core interface for all order and quote requests. This documentation describes how to test your CloudCore API and CloudSignal integrations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |