Developer Portal
Your own API portal for the companies you work with
Suppliers, dealers and partners register on your branded portal, read the API reference, create their own keys and start calling — in test first, then live. Per API you choose: route calls through DataSynca so your upstream systems and credentials stay hidden, or let suppliers use your own API keys while the portal handles documentation and access.
What is a developer portal?
A developer portal is the front door of your APIs: documentation, sign-up, keys and support in one place, so an external developer can integrate without opening a ticket with your IT team. Most companies either build one from scratch or run it as a separate product next to their integration platform.
DataSynca Developer Portal runs on your own hostname with your branding and sits directly on the API Gateway and flows you already operate — one deployment, one audit trail, no separate product to run. Each API is published the way you want it: proxied through DataSynca, or called directly with the keys you issue, with DataSynca hosting the catalog, documentation, registration and approvals.
How a call travels
Supplier → your portal host → DataSynca → your API
When an API is proxied, key, grant, quota and request validation are checked before anything reaches your upstream API. APIs you publish with your own keys skip this path — suppliers call them directly.
Production — dsp_live_ keys
Authorization: Bearer dsp_live_••••Supplier app
Partner, dealer, wholesaler
Your portal host
api.yourcompany.com
DataSynca
Key · grant · quota · validation
Your upstream API
URL and credentials hidden
Test — dsp_test_ keys
Authorization: Bearer dsp_test_••••Supplier app
Your portal host
DataSynca
Test upstream or simulator
Answers from the OpenAPI document
A test key on a production URL, or a live key on a test URL, is refused before it reaches anything.
Proxied calls are recorded
Calls and Reports show each request per company, user, API, version and environment — with masked detail and CSV export.
Why teams ask for this
The situations a developer portal solves
These are the requests integration teams get from sales, procurement and partners — Developer Portal is built for them.
Supplier and dealer onboarding
A new wholesaler registers, you approve it for the customer type and environment it needs, and it is calling your order API the same day — no e-mail chains, no shared credentials.
APIs you cannot expose directly
Your ERP or legacy API was never built for the internet. Route it through DataSynca: the portal publishes it under your domain while DataSynca holds the real URL and credentials.
Test first, then go live
Partners build against the test environment, with simulated or real test answers, and switch to production only after you open it for them.
Retiring an old version cleanly
Deprecate a version with a note and a sunset date. It keeps working with warning headers, every company that uses it is notified, and you retire it when the date passes.
What you get
A complete partner API programme — not a documentation page
Developer Portal covers the whole path from a company's first registration to its monthly usage report.
Your hostname, your brand
Run the portal on a domain you own, with your logo, colours, welcome and terms text, and portal pages you design — in English, Turkish or both.
Registration and approvals
Companies register themselves. You approve per customer type and environment, link them to an existing company, and open production when they are ready.
Test and live keys
Suppliers create their own dsp_test_ and dsp_live_ keys. Rotate, revoke, set a validity period and per-key limits without touching your upstream.
API Products from OpenAPI
Import OpenAPI 3 or Swagger 2 documents and group endpoints into the products each customer type may call. Proxied APIs get request validation; own-key APIs are hosted as documentation with the security your document declares.
Quotas and rate limits
Limit policies set calls per time window and a monthly quota per company. Suppliers see their quota in the portal; you see every company's on one page.
Reports and call log
Calls, error rates, response times and quota use per company, user, API, version and environment — with CSV export and a call log with masked request and response detail.
How it fits
From your first API to a running partner programme
- 1
Set up the portal
Pick the hostname, add your branding, e-mail sender and terms, and turn the portal on inside your DataSynca deployment.
- 2
Import your APIs
Upload an OpenAPI document, fetch it from a URL, or publish a DataSynca flow as an API. Configure the test and production upstreams — or let test simulate answers.
- 3
Define who may call what
Group endpoints into API Products, assign them to customer types such as suppliers or wholesalers, and set limit policies.
- 4
Approve, monitor, evolve
Approve registrations, open production when a partner is ready, watch Calls and Reports, and deprecate old versions with a sunset date.
Before you decide
Questions integration leads ask first
Short answers to what usually comes up in the first conversation.
Do suppliers get access to our internal systems?
Not unless you want them to. With a proxied API, suppliers call your portal host with their own key; DataSynca checks the key, the company's grants, limits and the request format, then forwards the call using credentials stored inside your deployment, so the upstream address and credentials are never shown to them. With an own-key API they use the keys you issued, against the address you published.
Do all calls have to go through DataSynca?
No. You decide per API. In the proxy mode DataSynca checks the key, the company's grants, limits and the request format, forwards the call, and records it in Calls and Reports; your upstream URL and credentials stay hidden. In the own-key mode suppliers call your API directly with the keys you issue — DataSynca hosts the catalog, documentation, registration and approvals, and nothing is proxied or metered.
Can suppliers use the portal without a DataSynca account?
Yes. Portal accounts are separate from DataSynca users. A supplier registers on the portal, verifies its e-mail, waits for your approval and then manages its own keys, usage and requests there. Portal accounts cannot sign in to your DataSynca console.
How do test and production work?
Each API version has a test and a production environment with its own upstream. Test keys start with dsp_test_ and only work on test URLs; live keys start with dsp_live_ and only work on production URLs. Test can answer from the OpenAPI document instead of calling a real system.
What happens when a company exceeds its quota?
Its limit policy decides: either further calls are refused until the next month, or calls continue and the quota works as a warning. Company contacts and your administrators are e-mailed as the quota fills up, and every answer carries limit and quota headers.
Does the portal need its own licence or infrastructure?
No. Developer Portal is part of your dedicated DataSynca deployment. It needs a hostname pointed at your installation and an SMTP account for the e-mails it sends. Which APIs and companies it should serve is something we go through with you.
Need to open your APIs to partners without opening your systems?
Tell us which APIs and which companies — we'll show how Developer Portal fits your dedicated deployment.