M7 Services
Use M7 services to store files, convert documents, publish content, exchange short-lived payloads, deliver messages, maintain relationships, or load permission catalogues. Each service has its own API, resources and access rules.
Start with choosing a service, then follow workspaces and access and the selected API reference. For sign-in and application registration, use M7 Identity and API User. The Identity SDK provides website and command-line integration guidance.
Service references
| Service | Integration task | API reference |
|---|---|---|
| BigFS | Store versioned objects in buckets, link vaults and run storage tasks. | BigFS |
| Document | Convert, inspect, sanitize and extract documents in an accessible bucket. | Document |
| Blog | Manage publications, content, media and revisions, and render published content. | Blog |
| Dead Drop | Create encrypted, time-limited payload handoffs and retrieve them once. | Dead Drop |
| Post | Manage message templates and policies and run notification or email-proof jobs. | Post |
| Mailbox | Send project-scoped email and inspect outbound attempts and delivery logs. | Mailbox |
| Relationship | Maintain scoped connections, resource memberships, enrollment requests and event receipts. | Relationship |
| Capability | Read owner-enabled, versioned permission catalogues and resolve published definitions. | Capability |
Begin an integration
- Choose the service and read its production base URL, supported methods and authorization guide.
- Register the application and acquire the credential profile required by that receiving service. Use its exact audience and any required proof.
- Select the personal or organization workspace, then the authorized project, bucket or publication. Load the applicable resource context and capabilities.
- Follow the service's request, response, pagination and lifecycle contract. Handle its HTTP errors and application envelope together.
Keep the service and resource identifiers returned by each API. Shared identity, organization references or catalogue definitions do not confer resource access. The selected service's authorization and resource guides define that access.