Introduction

This guide walks you through using the OriginStamp API actual request and response examples. We mainly focus on directly using the REST API via cURL. You can though use any other HTTP client to query the API.

Client Libraries

On top, we offer managed client libraries for different languages that make using OriginStamp as easy as possible.

• TypeScript: GitHub

Error Handling

OriginStamp's API uses standard HTTP status codes to indicate the success or failure of an API request along with a message to help identify the issue in most cases.

Common status codes include:

Status Code	Meaning	Description
200	OK	The request was successful.
202	Accepted	The request was received and a further action will trigger.
400	Bad Request	The request was invalid or missing required fields.
401	Unauthorized	Authentication failed or API key is missing.
403	Forbidden	The request is understood, but access is denied.
404	Not Found	The requested resource could not be found.
429	Too Many Requests	Rate limit exceeded.
500	Internal Server Error	Something went wrong. Please try again later or contact us.

In addition to these standard codes, certain API endpoints may define custom error cases with specific messages or error codes in the response body to provide more detailed feedback. These custom cases are documented per endpoint in our (API Reference)[https://redir.originstamp.com/api/docs].

We recommend handling these status codes appropriately in your integration to improve the robustness of your application.