OAuth 2.0 / OIDC
'Sign in with Hummer', consents and scopes. Standard flows with nothing to build yourself.
DevelopersAPI · MCP · SDK · Store
Connect, extend
and publish.
The ecosystem is open at the contract level: sign-in, data, actions, events, agents and schemas. Publishing to HummerStore is open to any developer after review.
6 stepsSandbox before publishing
App registration, sandbox tests, contract implementation, review, publication and version maintenance.
Integration surfaces
Eight ways to connect
All of them rest on the same HummerFabric contracts — there is no back door to the data.
REST API
Access to permitted read models and actions via Hummer Bridge contracts.
MCP
Connecting tools and sources for agents via the Model Context Protocol.
Webhooks
Subscribing to ecosystem events with delivery confirmation and retry.
Connector SDK
Building a connector to your system: read, write, events, permissions, health and tests.
Agent SDK
Publishing your own agent that works within granted permissions.
Schema Registry
Registering schemas and versions, checking compatibility across products.
Sandbox
A test environment with sample data to verify a connector or agent before publishing.
Examples
What connecting looks like
Short snippets for three typical tasks: sign-in, reading permitted data and subscribing to events.
GET /oauth2/authorize
?client_id=YOUR_CLIENT_ID
&redirect_uri=https://example.ru/callback
&response_type=code
&scope=openid profile context.read
&state=RANDOMThe standard OIDC authorization code flow. The user sees the requested scopes before consenting.
<code style="font-family:var(--em-font-mono);font-size:13px;line-height:1.7;color:var(--em-text-dim)">GET /v1/context/objects?type=invoice&since=2026-08-01 Authorization: Bearer ACCESS_TOKEN → 200 OK items[].source source system items[].fetched_at retrieval time items[].fields только разрешённые поля</code>
The response always carries provenance: the source system and the retrieval time.
<code style="font-family:var(--em-font-mono);font-size:13px;line-height:1.7;color:var(--em-text-dim)">POST /v1/webhooks
{ "event": "invoice.paid",
"url": "https://example.ru/hooks/invoice",
"secret": "SIGNING_SECRET" }
→ signed delivery, retry on failure,
подтверждение по коду 2xx</code>Undelivered events are retried by Hummer Continuity rules and never lost.
Console and documentation
What a developer gets
The Developer Console is part of HummerAuth: app registration, keys, redirect URIs and logs.
Developer Console
App registration, client_id, redirect URIs, scopes and request logs.
Test sandbox
An isolated environment with sample data: connectors and agents are verified before reaching users.
Schema Registry
Object schemas, versions and compatibility rules. A schema change goes through review.
Store publication flow
Submission, automated and manual review, publication, updates and version rollback.
Documentation navigation
Sections by product and by contract. AiHummer documentation is available already.
Version support
The compatibility contract: products update independently while contracts stay compatible.
Publication
Open submission, mandatory review
Any developer can publish a connector, an agent or an industry solution. Before publication an extension passes automated checks and a manual review: requested permissions, behavior, compatibility and support readiness.