API Development Company. Connect Your Systems.
We design and build REST APIs, and we integrate the systems you already run: ERP, CRM, payments, shipping and your own store. Webhooks, authentication, retries, versioning and documentation are part of the build, so the connection keeps working after launch.
What Do API Development and Integration Services Cover?
Devvista is a software development and growth agency that builds custom APIs and integrates business systems. API development means designing the endpoints other software calls: what you can ask for, what you send, what comes back and what happens when something is wrong. API integration means connecting systems that already exist so data flows between them, for example orders from a store into an ERP, or a closed deal in a CRM into an invoice.
Most of our integration work is a mix of both. A system with a good public API needs a careful client, field mapping and error handling. A system without one needs a small API layer of your own in front of it, so the rest of your stack talks to something stable. We write down which case you are in during scoping.
If the integration is part of a larger product, see custom software development. If it connects an ERP, see our Odoo implementation work, and for stores see ecommerce development.
Which kind of API work do you need?
| You have | You need | What we deliver |
|---|---|---|
| Two systems that both have APIs | An integration | A client, field mapping, retries, alerts and a log you can read |
| A legacy system with no API | An API layer in front of it | A small REST service, authentication and documentation |
| A product other developers will call | A public or partner API | Versioned endpoints, an OpenAPI description, rate limits and tests |
| Events you must react to (payments, orders) | Webhook receivers | We can add signature checks, a queue, duplicate handling and reconciliation |
API and Integration Work
Scope is written as a list of endpoints, events and fields before any code, so you know what you are paying for.
REST and JSON APIs
Resource-based endpoints with clear names, the right HTTP methods and status codes, input validation and consistent error bodies, built in Node.js or Python depending on your team. See also custom software development.
RESTERP integration
Orders, stock, invoices and customers kept consistent between your ERP and everything around it, including Odoo.
ERPCRM integration
Leads and deals flowing between forms, ads, your CRM and billing. Related: CRM development.
CRMPayment and shipping integrations
Payment events handled through webhooks, with verification and duplicate protection, plus shipping rates and labels pulled from carrier APIs into your checkout or back office.
PayWebhook receivers and senders
Endpoints that accept events from other systems safely, and the ability to send your own events to customers or partners.
HooksDocumentation and tests
We can provide an OpenAPI description, example requests and automated tests, so the next developer can use the API without calling us.
DocsHow We Build APIs That Last
Use the HTTP verbs as they are defined. MDN lists GET as safe and idempotent, and PUT and DELETE as idempotent but not safe. POST is neither, which is why retrying a POST without protection can create a second record. We design endpoints so a retry is harmless.
Make retries safe. Stripe documents idempotency keys for this: send a key with a request, and a retry after a connection error returns the saved result instead of repeating the operation. Stripe says v1 keys can be removed once they are at least 24 hours old, so a key is protection for a retry window, not a permanent record. We would apply the same pattern to an API we build.
Handle rate limits properly. A 429 status means the client sent too many requests in a given time, and the response may carry a Retry-After header saying how long to wait. We would have the client read it and slow down instead of hammering the server.
| Risk | What we would do about it |
|---|---|
| Retry creates a duplicate | Use idempotency keys and event ID logging |
| Too many requests | Honour 429 and Retry-After, queue the rest |
| Fake webhook call | Verify the signature header before acting |
| Leaked credentials | Scoped keys in a secrets store, with a rotation list |
Authenticate with the right tool. OAuth 2.0 is the framework that lets a third-party application obtain limited access to an HTTP service, which is why it is the usual choice when your customers connect their own accounts. For server-to-server links, scoped API keys kept in a secrets store are often simpler. We recommend one per integration and list the permissions each needs.
We check APIs we build against the OWASP API Security Top 10 (2023 edition), which starts with broken object level authorization and broken authentication.
Odoo to a Store Through the Odoo API
Which Odoo API to build on. Odoo's 19.0 documentation describes a JSON-2 API: you post a JSON object to the /json/2/<model>/<method> URL with an Authorization header carrying a bearer API key, and a database name header is optional. The same page says the older XML-RPC and JSON-RPC endpoints (/xmlrpc, /xmlrpc/2 and /jsonrpc) are scheduled for removal in Odoo 22 (fall 2028) and Odoo Online 21.1 (winter 2027).
A new integration should target JSON-2, and an old one built on the RPC endpoints needs a migration plan. Re-check the page for your version before you build.
| Odoo detail | What the documentation says |
|---|---|
| Endpoint | POST a JSON object to /json/2/<model>/<method> |
| Authentication | Authorization header: bearer followed by an API key |
| Old RPC endpoints | /xmlrpc, /xmlrpc/2 and /jsonrpc scheduled for removal in Odoo 22 (fall 2028) and Odoo Online 21.1 (winter 2027) |
| Plan requirement | External API only on Custom Odoo pricing plans |
A plan check comes first. The same documentation says external API access is only available on Custom Odoo pricing plans, not the entry-level plans the documentation lists. We confirm your plan in the first call, because it changes the design.
The store side. Shopify's documentation says an app should not rely on receiving data from webhooks alone, because delivery is not always guaranteed, and recommends reconciliation jobs that fetch changed objects, for example with an updated_at filter. It also says to ignore duplicate deliveries using the X-Shopify-Webhook-Id header and lists an X-Shopify-Hmac-Sha256 header for verifying that a delivery came from Shopify. Our design therefore uses webhooks for speed and a scheduled reconciliation job for correctness.
The same shape applies to other stores and ERPs. For the Shopify case in depth, read our Shopify ERP integration guide, and for the ERP side see Odoo customization.
Real scope varies with fields, volume and your Odoo setup.
From Spec
to Stable Integration
You review the endpoint and field list before we build, and test results before anything touches live data.
Map systems and data
We list each system, its API or lack of one, the fields that must match, and which system is the source of truth for each.
Write the contract
Endpoints, events, field names, error cases and authentication are agreed in writing, as an OpenAPI description where you are exposing an API.
Build behind a staging copy
We build against sandbox or staging accounts, never your live data first.
Add safety layers
We would add validation, retries with idempotency, duplicate checks, rate-limit handling, signature verification and secrets storage.
Test failure on purpose
We simulate slow responses, expired keys, duplicate events and a system that is down, and confirm the alert and recovery path.
Document and hand over
We can hand over the contract, a runbook, a credential rotation list and monitoring so a failure reaches the right person.
What Drives the Price of an Integration
Each quote is written to scope after a short call, and we ask for the budget you have in mind so the proposal fits it. Cost follows the amount of work, the systems it must connect to and the level of developer it calls for. A public API with versioning, documentation, rate limits and a partner portal sits much higher. Third-party fees, such as a vendor's API plan, are paid to that vendor.
| Cost driver | Pushes the price up when | Keeps it down when |
|---|---|---|
| API quality of each system | Poor docs, limits or no sandbox | Documented API with a test environment |
| Direction of data | Two-way sync with conflict rules | One-way push or pull |
| Real-time needs | Events must arrive in seconds and in order | A scheduled batch is enough |
| Security and audit | Customer-facing OAuth, role scopes, audit logs | Internal service with scoped keys |
| Documentation and tests | Public API with SDK examples | Internal use with a short runbook |
See also the custom software cost guide and the plain-English webhook vs API explainer ERP consulting: requirements and a costed roadmap before connecting systems.
Integrations We Have Already Delivered
Six platforms in one intake flow. A single Make automation connects Typeform, GoHighLevel, Airtable, Claude AI, Google Docs and Slack, syncs a 112-field intake into the CRM and the database without losing fields, and holds delivery behind a human approval. Read the Make lead intake case study.
Four named platforms around an AI analysis system. The credit repair build connects GoHighLevel, Relevance AI, Make.com and Airtable around a 17-agent analysis system with human checkpoints. See the Harold credit repair case study.
Ad platform feedback loop. For a mortgage and finance client, Make, Typeform and GoHighLevel pass qualification data back to Meta through the Conversions API, with a search-match-update step that prevents duplicate CRM records. See the Meta Ads CRM automation case study.
These are workflow-heavy builds rather than public APIs. If you need a public or partner API, ask on the call for what we can show and what stays under NDA.
APIs &
Tools
The list is what our case studies show. We can also work with Odoo, Shopify, Stripe, n8n and other stacks, so tell us yours.
Where the Tool Facts Come From
The API behaviour described above (status codes, retries, signatures, key rotation) comes from the specifications and vendor docs listed here, read in November 2026. Docs get revised, so open the link before you build on a detail.
- Odoo 19.0 external API: JSON-2 endpoint, bearer API key, RPC removal dates, Custom plan requirement
- Shopify webhooks: delivery not guaranteed, reconciliation, duplicate and HMAC headers
- Stripe idempotent requests: idempotency keys and 24-hour pruning for API v1
- Stripe webhooks: signature header, quick 2xx response, duplicate events
- MDN HTTP methods: safe and idempotent methods
- MDN 429 status: rate limiting and Retry-After
- RFC 6749: OAuth 2.0 authorization framework
- OpenAPI Specification: standard, language-agnostic interface to HTTP APIs
- OWASP API Security Top 10 2023: list of risks
Straight
Answers.
Plain answers to what we are asked before an integration is built.
Tell Us About Your Integration.
We will review it and come back with honest feedback and a clear estimate, no pressure, just a real conversation.
- 30-minute consultation
- NDA signed on request
- Reply within 24 hours
- Book a call30 minutes, no pitch. Tell us what you want to build.
- Get a straight answerHonest feedback on fit, scope and timeline.
- Decide with no pressureMove ahead only if it feels right. No commitment required.