API gateway for partners
Give partners one reliable endpoint: sync when they need an answer, async when they need speed.
Bitween API gateways accept documents over HTTPS, authenticate the calling partner, validate the body and run that partner's pipeline, returning the exchange id at once, or the downstream response when it's ready.
How it works
Four things to know.
Async for throughput
/async stores the exchange and returns 202 Accepted with its id straight away, while processing continues on queues.
Sync for answers
/sync waits for the result and returns the handler's response body and content type, or the flagged bad response with a 400.
Checks in a deliberate order
Unknown gateway, unknown key, unattached partner, deactivated gateway, inactive pipeline. Deactivation is checked after authorization, so only attached partners learn the gateway exists.
Validation before storage
Validators run synchronously and return their errors to the caller. Nothing is stored for invalid input.
curl -X POST "https://bitween.example.com/api/gateway/orders/async" \
-H "partnerkey: <partner API key>" \
-H "Content-Type: application/json" \
-d '{"order": {"id": "SO-1001"}}'
# 202 Accepted
# "7f3a91c2e4b04d8f9a0c51d2b7e6f310"Outcomes
What your team gets.
- Partners integrate against one stable URL per process
- Invalid documents rejected with reasons, never stored
- Different pipelines per partner behind the same endpoint
- Every call becomes a searchable exchange
Good to know: Sync calls with a long Wait-Period stay open until the exchange has a result, so always set a timeout on the client or proxy.
Documentation
Read the details.
Industries
Where this pattern shows up.
Put every integration on one governed pipeline.
Talk to the architects who build Bitween about your partners, systems and message volumes, or start from the docs and run it yourself today.