Magaya

Magaya is a logistics and supply chain software company whose cloud Digital Freight Platform runs freight forwarding, warehouse management, customs compliance, rate management, and a digital customer experience portal. Magaya exposes programmatic access to the logistics objects inside a customer's system - Shipments, Warehouse Receipts, Invoices, Items, and financial Transactions - through the Magaya API (a SOAP/XML Web Service) and the newer Magaya Open API collection of web services, plus a REST Digital Freight Portal API inherited from the Qwyk acquisition. API access is gated behind a Magaya subscription and a dedicated API user configured in the customer's own tenant (base URL of the form https://SYSTEMID.magayacloud.com/api); the reference documentation is public but runtime access requires a licensed system, so the resource paths below are honestly modeled from Magaya's published object model rather than confirmed against an open self-serve reference.

Magaya publishes 5 API contracts indexed on the APIs.io network, including Invoices API, Items API, Shipments API, and 2 more. Tagged areas include Logistics, Supply Chain, Freight Forwarding, Warehouse Management, and Shipping.

The Magaya catalog on APIs.io includes 1 Spectral governance ruleset.

Magaya’s developer surface includes engineering blog, authentication, documentation, API reference, signup flow, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

28.0/100 thin ▬ flat Agent 21/100 agent aware Front door AI 3/6 light Heartbeat 73/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

1 published contract

Logistics Supply Chain Freight Forwarding Warehouse Management Shipping Customs Transportation

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Freight Billing & Settlement Management

BC-2530

Invoices

POST /invoices

Warehousing Operations Management

BC-2460

Warehouse Receipts

POST /warehouse-receipts

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 28.0/100 · thin

Contract Quality 8.2 / 19

Developer Ergonomics 4.8 / 15

Access Clarity 2.2 / 15

Operational Transparency 1.2 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 0.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/magaya/"><img src="https://apis.io/badge/magaya/card.svg" alt="Magaya on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 14.9 — up to +17.0 composite points Ask about this →
Contract Quality scores 43.5 — up to +14.1 composite points Ask about this →
Developer Ergonomics scores 32.1 — up to +13.6 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/magaya/apis.yml: open an issue on github.com/api-evangelist/magaya to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Magaya Invoices API

Accounts-receivable invoices and their charge lines.

Magaya Items API

Item and commodity master data referenced across transactions.

Magaya Shipments API

Air, ocean, and ground shipment records and their tracking events.

Magaya Transactions API

Generic Magaya transaction documents - orders, bookings, quotes, releases.

Magaya Warehouse Receipts API

Cargo received into a Magaya-managed warehouse and inventory balances.

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Magaya API (Modeled) Invoices API

OPEN COLLECTION

Magaya API (Modeled) Invoices Items API

OPEN COLLECTION

Magaya API (Modeled) Invoices Shipments API

OPEN COLLECTION

Magaya API (Modeled) Invoices Transactions API

OPEN COLLECTION

Magaya API (Modeled) Invoices Warehouse Receipts API

OPEN COLLECTION

Magaya API (Modeled)

OPEN COLLECTION

Magaya API pricing

Not yet checked against Magaya's own pricing page. Compiled by API Evangelist on 2026-07-05 from www.magaya.com/; confirm before you rely on a figure.

Plan	Price
Magaya Digital Freight Platform Subscription enterprise	—
Digital Freight Portal (Qwyk) API enterprise	—

Plan details, limits and sources →

Rate limits

Magaya API Requests: not published requests
Digital Freight Portal REST API: not published requests
Auth0 Token Issuance: not published tokens

Compiled by API Evangelist, not yet checked against Magaya's documentation. Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

Magaya Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Magaya Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Magaya Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Magaya API Rules

60 rules · 58 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Magaya Authentication

http · 1 scheme

SECURITY

Magaya Domain Security

TLSv1.2 · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Magaya Agentic Access

14 operations · 4 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 4

The organization behind the API

Blog

Blog

BlogRSS

BlogRSS

LinkedIn

Website

Website

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: magaya
url: https://raw.githubusercontent.com/api-evangelist/magaya/refs/heads/main/apis.yml
name: Magaya
kind: company
description: Magaya is a logistics and supply chain software company whose cloud Digital Freight Platform runs freight forwarding,
  warehouse management, customs compliance, rate management, and a digital customer experience portal. Magaya exposes programmatic
  access to the logistics objects inside a customer's system - Shipments, Warehouse Receipts, Invoices, Items, and financial
  Transactions - through the Magaya API (a SOAP/XML Web Service) and the newer Magaya Open API collection of web services,
  plus a REST Digital Freight Portal API inherited from the Qwyk acquisition. API access is gated behind a Magaya subscription
  and a dedicated API user configured in the customer's own tenant (base URL of the form https://SYSTEMID.magayacloud.com/api);
  the reference documentation is public but runtime access requires a licensed system, so the resource paths below are honestly
  modeled from Magaya's published object model rather than confirmed against an open self-serve reference.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/magaya.png
x-docs-platform: stoplight
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Logistics
- Supply Chain
- Freight Forwarding
- Warehouse Management
- Shipping
- Customs
- Transportation
created: '2026-07-05'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: magaya:magaya-invoices-api
  name: Magaya Invoices API
  description: Accounts-receivable invoices and their charge lines.
  humanURL: https://www.magaya.com/magaya-open-api/
  baseURL: https://SYSTEMID.magayacloud.com/api
  tags:
  - Invoices
  properties:
  - type: OpenAPI
    url: openapi/magaya-invoices-api-openapi.yml
  - type: Documentation
    url: https://www.magaya.com/magaya-open-api/
  - type: APIReference
    url: https://developer.qwykportals.com/
  - type: PostmanCollection
    url: collections/magaya.postman_collection.json
  - type: OpenCollection
    url: collections/magaya.opencollection.json
- aid: magaya:magaya-items-api
  name: Magaya Items API
  description: Item and commodity master data referenced across transactions.
  humanURL: https://www.magaya.com/magaya-open-api/
  baseURL: https://SYSTEMID.magayacloud.com/api
  tags:
  - Item
  tags_raw:
  - Items
  properties:
  - type: OpenAPI
    url: openapi/magaya-items-api-openapi.yml
  - type: Documentation
    url: https://www.magaya.com/magaya-open-api/
  - type: APIReference
    url: https://developer.qwykportals.com/
  - type: PostmanCollection
    url: collections/magaya.postman_collection.json
  - type: OpenCollection
    url: collections/magaya.opencollection.json
- aid: magaya:magaya-shipments-api
  name: Magaya Shipments API
  description: Air, ocean, and ground shipment records and their tracking events.
  humanURL: https://www.magaya.com/magaya-open-api/
  baseURL: https://SYSTEMID.magayacloud.com/api
  tags:
  - Shipments
  properties:
  - type: OpenAPI
    url: openapi/magaya-shipments-api-openapi.yml
  - type: Documentation
    url: https://www.magaya.com/magaya-open-api/
  - type: APIReference
    url: https://developer.qwykportals.com/
  - type: PostmanCollection
    url: collections/magaya.postman_collection.json
  - type: OpenCollection
    url: collections/magaya.opencollection.json
- aid: magaya:magaya-transactions-api
  name: Magaya Transactions API
  description: Generic Magaya transaction documents - orders, bookings, quotes, releases.
  humanURL: https://www.magaya.com/magaya-open-api/
  baseURL: https://SYSTEMID.magayacloud.com/api
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/magaya-transactions-api-openapi.yml
  - type: Documentation
    url: https://www.magaya.com/magaya-open-api/
  - type: APIReference
    url: https://developer.qwykportals.com/
  - type: PostmanCollection
    url: collections/magaya.postman_collection.json
  - type: OpenCollection
    url: collections/magaya.opencollection.json
- aid: magaya:magaya-warehouse-receipts-api
  name: Magaya Warehouse Receipts API
  description: Cargo received into a Magaya-managed warehouse and inventory balances.
  humanURL: https://www.magaya.com/magaya-open-api/
  baseURL: https://SYSTEMID.magayacloud.com/api
  tags:
  - Warehouse Receipts
  properties:
  - type: OpenAPI
    url: openapi/magaya-warehouse-receipts-api-openapi.yml
  - type: Documentation
    url: https://www.magaya.com/magaya-open-api/
  - type: APIReference
    url: https://developer.qwykportals.com/
  - type: PostmanCollection
    url: collections/magaya.postman_collection.json
  - type: OpenCollection
    url: collections/magaya.opencollection.json
common:
- url: https://www.magaya.com/insights-by-magaya/
  type: Blog
- url: https://www.magaya.com/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/magaya-capability-edges.yml
  name: Magaya Business Capability Map
- type: AgenticAccess
  url: agentic-access/magaya-agentic-access.yml
- type: DomainSecurity
  url: security/magaya-domain-security.yml
- type: Authentication
  url: authentication/magaya-authentication.yml
- type: GitHubOrganization
  url: https://github.com/magaya-dev
- type: LinkedIn
  url: https://www.linkedin.com/company/magaya-corporation-inc-
- type: Website
  url: https://www.magaya.com/
- type: Documentation
  url: https://help.magaya.com/s/document-item?language=en_US&bundleId=magaya-api
- type: APIReference
  url: https://developer.qwykportals.com/
- type: SignUp
  url: https://www.magaya.com/start-here/
- type: Plans
  url: plans/magaya-plans-pricing.yml
- type: RateLimits
  url: rate-limits/magaya-rate-limits.yml
- type: FinOps
  url: finops/magaya-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Magaya API — frequently asked questions

Does Magaya have an API?

Yes. APIs.io lists 5 APIs from Magaya, including Magaya Invoices API, Magaya Items API and Magaya Shipments API, and 2 more.

Is there an OpenAPI specification for the Magaya API?

Yes. APIs.io indexes 5 OpenAPI specifications for Magaya, each linked for download from this page.

How do I authenticate with the Magaya API?

Magaya uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Magaya Authentication.

How much does the Magaya API cost?

APIs.io lists 2 pricing plans for Magaya, with each plan's price, limits and inclusions under Pricing on this page.

Is the Magaya API ready for AI agents?

Magaya has a Kin Score of 28.0 out of 100 (thin) and an Agent Readiness score of 20.7 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/magaya"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/magaya/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/magaya/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.