Magaya Warehouse Receipts API

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

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/magaya-warehouse-receipts-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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

OpenAPI Specification

magaya-warehouse-receipts-api-openapi.yml Raw ↑
openapi: 3.0.3
info:
  title: Magaya API (Modeled) Invoices Warehouse Receipts API
  description: 'A modeled REST representation of the Magaya logistics object model exposed to integrators of the Magaya Digital Freight Platform. Magaya''s own programmatic surfaces are (1) the Magaya API, historically a SOAP/XML Web Service reached at a per-tenant base of the form https://SYSTEMID.magayacloud.com/api and authenticated with a dedicated API user (username/password) configured inside the Magaya system; (2) the newer Magaya Open API, a collection of web services covering shipments, bookings, quotes, rates, invoices, bills, inventory balances, shipping events, document attachments, organization master data, and warehousing; and (3) the REST Digital Freight Portal API inherited from the Qwyk acquisition (developer.qwykportals.com), authenticated with Auth0 machine-to-machine OAuth clients.

    This OpenAPI document does NOT reproduce a confirmed open self-serve reference. Access to any Magaya API requires a licensed Magaya subscription and a configured API user, so the paths, parameters, and schemas here are honestly modeled from Magaya''s published object model (Shipments, Warehouse Receipts, Invoices, Items, and Transactions) to give integrators a starting map. Verify exact operation names, fields, and authentication against the documentation for your Magaya edition and version before building.'
  version: 0.1-modeled
  contact:
    name: Magaya
    url: https://www.magaya.com/
  x-access-model: Gated. Requires a Magaya subscription and an API user configured in the customer's own tenant. Public reference documentation exists, but there is no open self-serve API key signup. Base URL is per-tenant (https://SYSTEMID.magayacloud.com/api).
  x-endpoints-modeled: true
servers:
- url: https://SYSTEMID.magayacloud.com/api
  description: Per-tenant Magaya Cloud base URL. Replace SYSTEMID with your Magaya System ID. On-premises deployments expose an equivalent host on the customer's network.
security:
- apiUser: []
tags:
- name: Warehouse Receipts
  description: Cargo received into a Magaya-managed warehouse and inventory balances.
paths:
  /warehouse-receipts:
    get:
      operationId: listWarehouseReceipts
      tags:
      - Warehouse Receipts
      summary: List warehouse receipts
      parameters:
      - $ref: '#/components/parameters/Limit'
      - $ref: '#/components/parameters/Offset'
      responses:
        '200':
          description: A page of warehouse receipts.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/WarehouseReceipt'
        '401':
          $ref: '#/components/responses/Unauthorized'
    post:
      operationId: createWarehouseReceipt
      tags:
      - Warehouse Receipts
      summary: Create a warehouse receipt
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/WarehouseReceipt'
      responses:
        '201':
          description: The created warehouse receipt.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WarehouseReceipt'
        '401':
          $ref: '#/components/responses/Unauthorized'
  /warehouse-receipts/{guid}:
    get:
      operationId: getWarehouseReceipt
      tags:
      - Warehouse Receipts
      summary: Retrieve a warehouse receipt
      parameters:
      - $ref: '#/components/parameters/Guid'
      responses:
        '200':
          description: The requested warehouse receipt.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WarehouseReceipt'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  schemas:
    Error:
      type: object
      properties:
        code:
          type: string
        message:
          type: string
    WarehouseReceipt:
      type: object
      properties:
        guid:
          type: string
        number:
          type: string
        warehouse:
          type: string
        supplier:
          $ref: '#/components/schemas/Party'
        pieces:
          type: integer
        weight:
          type: number
        volume:
          type: number
        items:
          type: array
          items:
            $ref: '#/components/schemas/Item'
        receivedOn:
          type: string
          format: date-time
    Party:
      type: object
      properties:
        name:
          type: string
        address:
          type: string
        country:
          type: string
    Item:
      type: object
      properties:
        guid:
          type: string
        partNumber:
          type: string
        description:
          type: string
        unit:
          type: string
        weight:
          type: number
        volume:
          type: number
        onHand:
          type: number
          description: Current inventory balance.
  parameters:
    Limit:
      name: limit
      in: query
      required: false
      schema:
        type: integer
        default: 50
        maximum: 500
      description: Maximum number of records to return.
    Guid:
      name: guid
      in: path
      required: true
      schema:
        type: string
      description: The Magaya object GUID identifying the record.
    Offset:
      name: offset
      in: query
      required: false
      schema:
        type: integer
        default: 0
      description: Number of records to skip for pagination.
  responses:
    Unauthorized:
      description: Authentication failed or the API user is not authorized.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: The requested record was not found.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    apiUser:
      type: http
      scheme: basic
      description: Magaya API user. A dedicated API user (username and password) is configured inside the Magaya system, distinct from a regular login user. The Digital Freight Portal REST API instead uses Auth0 machine-to-machine OAuth client credentials.