Certification

Sigfox Certifications

Sigfox Certification Handbook

Helpful

Callbacks & APIAPI

API Response code references

Learn more about common error codes returned by Sigfox API and how to resolve them.

 

Sigfox API uses conventional HTTP response codes to indicate the success or failure of an API request. 

  • Codes in the “2xx” confirm that your request worked as expected

(can be handled programmatically - e.g.: an authentication error when registering a new device with an ID/PAC)). Please find below some error codes used:

 

200

Successful response

201

Created (item)

204

No Content (item successfully updated or deleted)

 

 

  • Codes in the “4xx” range indicate an error due to the request form (e.g. a required parameter missing, a resource was not found, etc.) or to the request non-conformity to the usage policy. You can handle these errors programmatically (e.g., an authentication error when registering a new device with an ID/PAC). Please find below some error codes used:

400

syntax or format error

401

Unauthorized (authentication issue)

403

Permission (access right) issue

404

If a requested entity doesn't exist

405

A request is not handled by the server

409

If trying to create an already existing entity

412

If a request parameter doesn't respect a condition

429

Too many requests

 

 

  • Codes in the 5xx range indicate an error with Sigfox servers.

500

sever error

 

Some additional information can be added in the body of the response. This information is dedicated to help human users to understand the issue. It can be changed by Sigfox with no prior notification and thus shall not be parsed in any platform integration.

 

Can't find what you're looking for ?

Have questions? Our worldwide Community of expert fans can answer them.
Have answers? Join the Community and help!

sigfoxask

Ask the community >