A REST API is a common style of API that uses standard web requests, such as GET to read and POST to create, to work with data at specific web addresses.
Integration · Reviewed by Ray Rasouli
Ask about REST API
Plain answers, with your setup in mind.
Ask anything about REST API. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
REST is the most widely used way modern business apps share data. Each type of record, like orders or customers, has its own web address, and you use simple verbs to read, create, update or delete it. Responses usually come back as JSON, a plain text format both people and machines can read.
If a retailer wants its online store to create sales orders in its accounting system, a developer can send a POST request with the order details to the accounting system's orders address.
Because REST follows web standards, most programming tools and integration platforms support it out of the box.
In practice
Errors are not handled.
A request can fail for many reasons, and integrations that do not check the response lose data silently.
Pagination is ignored.
Large lists come back in pages, and code that reads only the first page misses most of the records.
Retries create duplicates.
Resending a create request after a timeout can make two orders unless the API supports idempotency.
Field formats differ between systems.
Dates, currencies and units come back in formats that need converting before the other system accepts them.
Representational state transfer. In practice, people use it to mean an API built on standard web requests and addresses.
REST gives each resource its own address. GraphQL uses one address where the caller asks for exactly the fields it wants in one request.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.