> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.
# Malbek
> Malbek (Signature & Contract Management): the API posture, publish target and field mapping composerID publishes a decision reference through.
This page records how composerID publishes into Malbek: the vendor's API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it.
Malbek is a contract lifecycle management platform: agreements with configurable metadata fields, contract types and templates, clauses, obligations and approval workflows, plus Konnect connectors into CRM, procurement and e-signature systems. Its REST API is provided to customers but has no public endpoint reference, so the API posture here is indicative until confirmed at onboarding. composerID creates the services contract record (a Statement of Work or a managed service agreement) of the tenant's contract type and stamps the Intent ID into a client-defined field on that contract, reading status back by polling.
Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation). No developer portal is evident.
## Integration path
How composerID connects to this destination, at a glance.
| Step | Detail |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | Tenant-issued API credentials provisioned by Malbek for the customer's instance (API key or OAuth 2.0 client credentials; the grant type is indicative until confirmed at onboarding). |
| composerID publishes | Contract record: Malbek REST API: create Contract |
| Intent ID lands on | `Contract` `custom_fields.intent_id`, written into the destination record |
| Back-sync | Polling: the destination publishes no events composerID can subscribe to, so state is read back on a schedule. |
## Vendor documentation
## API posture
| Aspect | Detail |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | Tenant-issued API credentials provisioned by Malbek for the customer's instance (API key or OAuth 2.0 client credentials; the grant type is indicative until confirmed at onboarding). User sign-in federates to the customer's IdP via SAML SSO. |
| Style | REST, JSON (customer-gated reference; no public OpenAPI) |
| Base URL | Tenant-specific API host supplied by Malbek at provisioning; no public base URL is published |
| Webhooks | Konnect connectors push contract data into configured systems (CRM, procurement, e-signature) and workflow rules send notifications, but a general outbound webhook subscription API is not publicly documented. Treat as poll-first: read the contract back on a schedule. |
| Events posture | Polling |
| Rate limits | Not publicly published; confirm per tenant at onboarding and back off on 429. |
| Objects | Contracts (agreements) with contract type, status, dates, value and client-defined custom fields; contract types and templates; counterparties (companies, contacts); clauses and clause library; obligations; workflow and approval tasks; documents and e-signature envelopes via connectors |
## Publish target and field mapping
Each object below pairs the canonical intent fields with the destination's own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
| Mapping | Detail |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Canonical to destination | contract\_type (SOW or MSA), title, counterparty, service\_category, effective\_date, end\_date, value, cost\_center |
| Target | Malbek REST API: create Contract |
| Requirement | Required |
| Notes | Contract types and their fields are tenant-configured; fetch the type's field definitions first. Operation name and path indicative until confirmed at onboarding. |
| Mapping | Detail |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Canonical to destination | intent\_id -> custom\_fields.intent\_id (client-defined text field on the contract type) |
| Target | Contract custom (client-defined) field |
| Requirement | Required |
| Notes | An admin adds a text field named for the composerID reference to the SOW / MSA contract type; it is then searchable in contract lists. If the tenant will not add a field, fall back to link mode and composerID records the Malbek contract identifier on its side. Deep link https\://\{tenant\_host}/contracts/\{external\_id} (illustrative). |
| Mapping | Detail |
| ------------------------ | ----------------------------------------------------------------------------- |
| Canonical to destination | defence\_file\_ref -> contract document / attachment |
| Target | Contract document (attachment) |
| Requirement | Recommended |
| Notes | Attach as a supporting document on the contract, not as the executable paper. |
| Mapping | Detail |
| ------------------------ | ----------------------------------------------------------------------------- |
| Canonical to destination | status, executed\_date, signed document reference |
| Target | Malbek REST API: read Contract / list Contracts filtered on the custom field |
| Requirement | Read scope only |
| Notes | Polled on a schedule; Konnect pushes are tenant-configured and not relied on. |
Malbek's API reference is available to customers and partners, not on a public developer portal, so every endpoint, auth grant and limit above is indicative until confirmed with the tenant's Malbek team at onboarding. Contract types, their custom fields and the approval workflows are configured per tenant: the Intent ID field must be added to the SOW / MSA contract type before the first publish, and its filterability in contract search should be verified in the tenant. Konnect connectors (for example to e-signature or procurement) are licensed and configured separately.
## Next steps
The five ways composerID reaches a destination, and the minimum a destination must offer.
Plan, preflight and publish: how a decision becomes a valid record in a destination.
Every destination composerID documents, with its category and coverage status.