01
Capability contracts
Exact capability IDs, actions, command boundaries and organization scope instead of undocumented internal endpoints.
AVANTIQO DEVELOPERS
Build software on the business system Avantiqo already governs.
Discover exact capabilities, issue scoped machine credentials, separate environments, call versioned APIs, receive signed events, inspect request evidence and meter usage — all against the same organization context that runs the business.
Capability contractsScoped machine identitySigned eventsObservable + metered
AVANTIQO DEVELOPERS
Organization-scoped developer control plane
PRODUCTION BOUNDARIES ON
Overview
Capabilities
API Explorer
Credentials
Webhooks
Logs
Usage
API Explorer
200 OK
Capability
work-requests
entity_id
current entity
period_id
current period
GET /api/developer/v1/operations/work-requests
Authorization: Bearer $AVANTIQO_TOKEN
X-Avantiqo-Environment: production
✓ organization scope bound
✓ capability authority verified
✓ request evidence recorded
Webhooks
invoice.postedDELIVERED
staff.updatedDELIVERED
developer.testRETRYING
Usage & health
Requests
1,284
p95
182ms
Failures
0.3%
Quota
28%
Identity
Scoped credential
Context
Org · entity · period
Evidence
Request ID · audit
ENVIRONMENTS · CREDENTIALS · API · WEBHOOKS · EVIDENCE
THE DEVELOPER CONTROL PLANE
From first credential to verified production traffic.
Avantiqo Developers is the operating surface around the API: discover exact contracts, bind organization context, issue scoped credentials, separate environments, receive signed events, inspect failures and understand usage before a customer integration reaches production.
02
Machine identity
Issue, rotate and revoke scoped credentials. Production identities remain separate from development and staging.
03
Business context
Requests carry the exact organization and, when needed, entity, period, record and domain context.
04
Signed events
Subscribe to committed business events through environment-bound webhooks with delivery evidence and replay controls.
05
Observability
Request IDs, status, latency, permission failures, throttling and webhook health stay visible to the developer.
06
Usage & economics
Rate and monthly capacity, provider-backed usage and metered workloads remain visible instead of arriving as a surprise bill.
THE IMPORTANT DIFFERENCE
You are not integrating with a blank data API. You are integrating with governed business records already connected inside Avantiqo — customers, invoices, employees, legal entities, documents, permissions, operations and evidence — through the authority granted to your integration.
GOVERNED BUSINESS CONTEXT
Your integration inherits the business context Avantiqo already protects.
Developers work with records that already belong to an organization, legal entity, person, customer, period or workflow. The developer identity is separate from employee identity; permissions and evidence stay attached to the exact organization and capability instead of being rebuilt in every app.
Example · workforce identity context
Verified identity
When a capability touches workforce data, the employee's verified contact and staff identity remain connected to that governed record.
Private evidence
Passport, national ID and optional work permit remain restricted, versioned records.
Legal entity
Employment and work-permit context stay tied to the correct organization and employer.
Expiry state
Validity and expiry remain part of the business record instead of a spreadsheet reminder.
Authority
Human and machine actions stay permission- and capability-bound.
Audit
Access, requests, decisions and execution evidence remain traceable.
HOW DEVELOPMENT ACTUALLY WORKS
From a business job to a verified production integration.
Avantiqo does not give an integration broad database access and ask the developer to recreate business rules. You select an exact governed capability, grant the minimum machine authority, prove the request in a safe environment, then move live execution into Production with durable evidence around every request and event.
01
Choose capability
Find the exact contract, commands, events and boundary in the live catalog.
02
Choose environment
Use Development or Staging for read-safe validation. Keep live authority separate.
03
Issue credential
Create an environment-bound machine identity with the smallest Operations scopes needed.
04
Prove a read
Use API Explorer to confirm organization context, headers, response shape and request evidence.
05
Add live command
Only Production credentials can mutate business state. External mutations require idempotency.
06
Subscribe to events
Production webhooks receive committed Operations events; non-production receives test events only.
07
Operate with evidence
Use request IDs, logs, webhook delivery state, quotas and metered usage to diagnose and control the integration.
Development
Read-only against the live organization data plane. Use for safe contract and connectivity validation.
Staging
Also read-only today. Use for pre-production application testing without live mutation authority.
Production
The live machine environment. Write scopes, live business mutations and committed business-event subscriptions belong here.
Capability catalog
Business capabilities, not another software suite.
The authenticated Developer Portal currently exposes the canonical Operations and Commerce execution registry. Each capability has an exact lifecycle, commands, events, read/write boundary and ownership rules so an external application does not have to guess which domain is authoritative.
EXE
Execution
Create and control operational work from intake through accountable execution.
Work RequestsWork OrdersWork ItemsRunsRecurring WorkWork History
PLN
Planning
Plan workload, capacity, resources, work schedules and operational scenarios without taking ownership away from People or other source domains.
Operational PlansCapacity PlanningWork SchedulesAppointment WindowsPlanning ScenariosDemand Signals
ORC
Orchestration
Queue, route, dispatch, assign and coordinate operational work across eligible resources and execution nodes.
QueuesDispatchRoutingAssignmentsHandoffsLoad Balancing
RES
Resources
Work with Operations-owned resources while preserving People, Assets and Administration as the authority for their own master data.
ResourcesWork CentresEquipmentDevicesAvailabilityReservations
CTL
Control
Govern procedures, checklists, evidence, approvals, release rules and operational policy around execution.
ProceduresChecklistsCompletion EvidenceSign-offsApprovalsPolicy Exceptions
RSK
Resilience
Handle incidents, exceptions, investigations, corrective actions, escalations and operational recovery through governed lifecycles.
IncidentsInvestigationsRoot CauseCorrective ActionsEscalationsContinuity Plans
QLT
Quality
Plan and execute inspections, checks, non-conformance handling, rework and operational audits with retained evidence.
Quality PlansInspectionsChecksNon-conformancesReworkOperational Audits
KPI
Performance
Read and control operational service levels, KPIs and performance evidence such as throughput, lead time, backlog and utilisation.
Service LevelsKPIThroughputCycle TimeBacklogScorecards
INT
Operational Intelligence
Observe the immutable operational event stream, live state, alerts, thresholds, forecasts and audit evidence.
Operational EventsMonitoringAlertsForecastingAudit TrailCommand Centre
COM
Commerce Execution
Run neutral commerce execution while Commercial, Supply Chain and Finance remain authoritative for their own records and accounting.
Point of SaleOrder CaptureCheckoutReceiptsCash ControlFulfillment Dispatch
This is the current Developer API surface. Broader Avantiqo products such as Finance, People, Documents, Creative and Intelligence remain separate product/domain surfaces unless and until their exact contracts are registered for Developer API exposure. The portal shows the live registry rather than implying access that does not exist.
Integration model
Choose the level of control you need.
Developer tooling is the control plane for building and operating an integration: contracts, environments, credentials, API exploration, signed events, SDKs, logs and usage. The separate API Platform explains the direct metered capability surface; both use the same governed Avantiqo business capabilities underneath.
01
API Explorer
Inspect exact capability contracts, organization context and safe requests before writing integration code.
02
Environments
Separate development, staging and production machine identities and release boundaries.
03
SDKs
Generate client starters from current Avantiqo capability contracts for application code.
04
Webhooks
Receive signed committed business events with delivery evidence, retry and replay controls.
05
Observability
Trace request IDs, failures, latency, throttling and quota health from the developer control plane.
06
Production governance
Move from read-safe validation to live authority only through explicit Production controls, least-privilege scopes and durable request evidence.
One engine, multiple surfaces
The same capability can power Avantiqo or your product.
Compose Avantiqo capabilities into your own application while organization scope, permissions and execution records stay consistent.
ONE GOVERNED CAPABILITY
ORGANIZATION · AUTHORITY · EVIDENCE
Capability runtime
operations.work-requests
organization_id → bound
entity_id → optional context
credential scope → enforced
request_id → evidence
✓ same business rules regardless of surface
Avantiqo Business
Native workspace uses the same capability contract.
External application
Your product calls the versioned Developer API.
Staff / customer portal
Role-specific experiences stay on the same business record.
Connected application
Your external application can call the same governed Operations contract through the Developer API.
Authority
Same organization + permission boundary
Events
Same committed business event stream
Evidence
Same request, audit and verification trail
01
SDK
02
Webhook
03
Environments
04
API Explorer
05
Production governance
WHICH AVANTIQO DEVELOPER SURFACE?
Developers, APIs, GPU compute and Code Studio solve different jobs.
They share the same Avantiqo business system underneath, but they are intentionally separate so integration authority, commercial API use and software engineering do not get mixed together.
Developers
Build and operate an external integration
Use the authenticated Developer Portal for capability contracts, environments, machine credentials, API Explorer, webhooks, SDKs, logs, quotas and usage.
Open Developer Portal →API Platform
Consume Avantiqo as a metered capability API
Use this when a product needs direct, commercial capability calls and the main question is what API service is available, how it is priced and how it is consumed.
Explore API Platform →GPU Compute
Run demanding accelerated workloads
Use metered GPU capacity for AI, inference, training, rendering and production workloads that need dedicated compute beyond ordinary application execution.
Explore GPU Compute →Code Studio
Design, change and build software with Avantiqo
Use Code Studio when the job is software engineering itself: discuss architecture, inspect code, build features, preview UI, review diffs and execute governed code changes.
Explore Code Studio →DEV
Build with Avantiqo at the level your product needs.
Use this developer area to understand available capabilities, integration patterns and the tools for building on Avantiqo. Organization owners/admins can use the control plane directly, while external developers join through organization-scoped Developer Portal invitations without becoming staff. The authenticated Developer Portal contains the live control plane: capability contracts, environments, scoped credentials, API Explorer, signed webhooks, generated SDKs, request logs, quotas and usage. Development and Staging remain read-only against live business data; Production is the governed boundary for live mutations and committed business events.