Skip to main content
Have a project in mind? Let's talk
Book a call Tell us about your project Book a Call
API
  API Development and Integration

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.

WrittenQuote to scope
BudgetAgreed up front
24hReply time
API Development API Integration Services ERP Integration CRM Integration Payment Webhooks OAuth and API Keys Odoo API System Integration API Development API Integration Services ERP Integration CRM Integration Payment Webhooks OAuth and API Keys Odoo API System Integration

What Do API Development and Integration Services Cover?

An API is a contract between two systems. Good work makes that contract clear, secure and hard to break.

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 haveYou needWhat we deliver
Two systems that both have APIsAn integrationA client, field mapping, retries, alerts and a log you can read
A legacy system with no APIAn API layer in front of itA small REST service, authentication and documentation
A product other developers will callA public or partner APIVersioned endpoints, an OpenAPI description, rate limits and tests
Events you must react to (payments, orders)Webhook receiversWe 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.

01

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.

REST
02

ERP integration

Orders, stock, invoices and customers kept consistent between your ERP and everything around it, including Odoo.

ERP
03

CRM integration

Leads and deals flowing between forms, ads, your CRM and billing. Related: CRM development.

CRM
04

Payment 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.

Pay
05

Webhook receivers and senders

Endpoints that accept events from other systems safely, and the ability to send your own events to customers or partners.

Hooks
06

Documentation and tests

We can provide an OpenAPI description, example requests and automated tests, so the next developer can use the API without calling us.

Docs

How We Build APIs That Last

Most integration failures come from the unglamorous parts: retries, duplicates, expired credentials and silent changes.

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.

RiskWhat we would do about it
Retry creates a duplicateUse idempotency keys and event ID logging
Too many requestsHonour 429 and Retry-After, queue the rest
Fake webhook callVerify the signature header before acting
Leaked credentialsScoped 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

A common request: keep stock and orders in sync between an Odoo database and an online store.

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 detailWhat the documentation says
EndpointPOST a JSON object to /json/2/<model>/<method>
AuthenticationAuthorization 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 requirementExternal 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.

01
Step One

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.

02
Step Two

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.

03
Step Three

Build behind a staging copy

We build against sandbox or staging accounts, never your live data first.

04
Step Four

Add safety layers

We would add validation, retries with idempotency, duplicate checks, rate-limit handling, signature verification and secrets storage.

05
Step Five

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.

06
Step Six

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

The number of fields rarely matters. The number of failure cases does.

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 driverPushes the price up whenKeeps it down when
API quality of each systemPoor docs, limits or no sandboxDocumented API with a test environment
Direction of dataTwo-way sync with conflict rulesOne-way push or pull
Real-time needsEvents must arrive in seconds and in orderA scheduled batch is enough
Security and auditCustomer-facing OAuth, role scopes, audit logsInternal service with scoped keys
Documentation and testsPublic API with SDK examplesInternal 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

The three builds below are real, and the clients are described only as far as their case studies allow.

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.

Make GoHighLevel Airtable Typeform Webhooks REST Node.js Python PostgreSQL

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.

Straight
Answers.

Plain answers to what we are asked before an integration is built.

Still have a question?Send it over and we will answer personally.Send a Message

An API development company designs and builds the endpoints other software calls, and connects your systems to each other and to third-party platforms. The work includes authentication, validation, error handling, versioning, documentation and tests, not only the code that returns data.

API integration services connect systems that already exist so data moves between them, for example a store and an ERP, or a CRM and a billing tool. A good integration also handles retries, duplicates, rate limits and alerts so that a failure is noticed and fixed.

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. Vendor API fees are paid to the vendor.

Yes. Odoo documents a JSON-2 API at /json/2/ with bearer API key authentication, and says the older XML-RPC and JSON-RPC endpoints are scheduled for removal. External API access is only available on Custom Odoo pricing plans, so we check your plan first. See the worked example on this page.

An API is something you call to ask for or send data. A webhook is the reverse: another system calls your endpoint when an event happens. Most integrations use both, webhooks for speed and API calls to reconcile anything missed. Our webhook vs API article explains it in detail.

We check for an existing record before creating one, use idempotency keys where an API supports them, and log event IDs so a repeated delivery is ignored. Our Meta Ads CRM case study uses a search-match-update step for this reason.

OAuth 2.0 when your customers connect their own accounts, and scoped API keys in a secrets store for server-to-server links. We recommend one per integration and list the permissions each needs.

Yes, we can provide an OpenAPI description for APIs you expose, example requests and automated tests, plus a short runbook for integrations.

Then we put a small API layer of your own in front of it, or look at other supported integration routes such as file exports. We tell you in scoping which route is realistic and what it costs.

Yes. We sign a mutual NDA on request before detailed conversations. Several of our integration case studies are for confidential clients.
Let's talk

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
  1. Book a call30 minutes, no pitch. Tell us what you want to build.
  2. Get a straight answerHonest feedback on fit, scope and timeline.
  3. Decide with no pressureMove ahead only if it feels right. No commitment required.
Chat on WhatsApp