Create B2B messages

post

/fscmRestApi/resources/11.13.18.05/b2bMessages

Request

Header Parameters
  • This is the service provider ID if a service provider is used to send B2B messages, for example, XYZ Service Provider. If Agent information isn't passed as a header, it's assumed that no service provider is being used, that is, the value for service provider is None.
  • This is the type of service provider ID if a service provider is used to send B2B messages, for example, Name. If Agent information isn't passed as a header, it's assumed that no service provider is being used, that is, the value for service provider is None.
    Example:
    Name
  • Specifies the type of content being sent to the server. The valid value is application/xml.
    Example:
    [
        "application/xml"
    ]
  • Type of document that's being sent
    Example:
    [
        "AcknowledgeChangePurchaseOrder",
        "AcknowledgePurchaseOrder",
        "SupplyPlanningData",
        "AcknowledgeInvoice",
        "ProcessForecast",
        "SupplyForecast",
        "AcknowledgeReceiptAdvice",
        "ProcessInvoice",
        "ProcessShipment",
        "ProcessReceiptAdvice",
        "ProcessPurchaseOrder",
        "ChangePurchaseOrder",
        "CancelPurchaseOrder",
        "CreditNote"
    ]
  • Prefer is an optional header. If the Prefer header is specified with the value respond-async, the service will process the request asynchronously. If the Prefer header is not included, the response will be handled synchronously.
    Example:
    respond-async
  • This is the ID of the party that's sending the B2B message; the trading partner ID, for example, ABC Company.
  • This is the type of ID of the party that's sending the B2B message; the trading partner ID type, for example, Name.
    Example:
    [
        "Generic",
        "DUNS",
        "Direct",
        "GLN",
        "MISC",
        "NetworkID",
        "Name",
        "PHONE",
        "TAXID"
    ]
Supported Media Types
Request Body - application/xml ()
Root Schema : schema
Type: object
Show Source
Nested Schema : ApplicationArea
Type: object
Show Source
Nested Schema : DataArea
Type: object
Show Source
Nested Schema : Receiver
Type: object
Show Source
Nested Schema : Sender
Type: object
Show Source
Nested Schema : Invoice
Type: object
Show Source
Nested Schema : Process
Type: object
Nested Schema : InvoiceHeader
Type: object
Show Source
Nested Schema : InvoiceLine
Type: object
Show Source
Nested Schema : Extension
Type: object
Show Source
Nested Schema : ShipToParty
Type: object
Show Source
Nested Schema : Location
Type: object
Show Source
  • Ship to location ID (e.g., 'GE-PM_HQ')
    Example: GE-PM_HQ
Nested Schema : InvoiceCharge
Type: object
Show Source
Nested Schema : PurchaseOrderReference
Type: object
Show Source
Nested Schema : UnitPrice
Type: object
Show Source
Nested Schema : LineIDSet
Type: object
Show Source
Back to Top

Response

Supported Media Types

200 Response

Successful Processing
Body ()
Root Schema : jsonErrorResponse
Type: object
Show Source
Nested Schema : error
Type: array
Show Source
Nested Schema : items
Type: object
Show Source

202 Response

Request has been accepted for processing, but processing has not been completed or may not have started.
Body ()
Root Schema : jsonErrorResponse
Type: object
Show Source
Nested Schema : error
Type: array
Show Source
Nested Schema : items
Type: object
Show Source

400 Response

Bad Request - Various Error Scenarios
Body ()
Root Schema : xmlErrorResponse
Type: object
Show Source
Nested Schema : error
Type: array
Show Source
Nested Schema : items
Type: object
Show Source

401 Response

Invalid User - Unauthorized

403 Response

User is Not Authorized

415 Response

Unsupported Media Type

500 Response

Internal Server Error
Body ()
Root Schema : schema
Type: object
Show Source
Nested Schema : error
Type: object
Show Source
Back to Top