How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Emburse Shipping Addresses API

The Shipping Addresses API from Emburse — 2 operation(s) for shipping addresses.

Emburse Shipping Addresses API is one of 48 APIs that Emburse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Shipping Addresses. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.emburse.com/v1, https://api.emburse-qa.com/v1.

5 operations 2 paths 1 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.emburse.com/v1/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Emburse Shipping Addresses API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — OAuth2 access token. Include in Authorization header: Authorization: Bearer YOURACCESSTOKEN

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Shipping Addresses 5
GET
/shipping-addresses
Get shipping addresses
get_shipping_addresses 5 params → 200400401403404409429500
POST
/shipping-addresses
Post shipping addresses
post_shipping_addresses body → 201400401403404409429500
GET
/shipping-addresses/{id}
Get shipping addresses by id
get_shipping_addresses_by_id 4 params → 200400401403404409429500
PUT
/shipping-addresses/{id}
Put shipping addresses by id
put_shipping_addresses_by_id 4 params body → 200400401403404409429500
DELETE
/shipping-addresses/{id}
Delete shipping addresses by id
delete_shipping_addresses_by_id 4 params → 204400401403404409429500

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is APIShippingAddress (10 properties). Each schema is shown below with its type and property counts.

APIShippingAddress
object
10 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emburse-shipping-addresses-api-openapi.yml Raw ↑

Other APIs Emburse publishes across the network.

Emburse Professional API
Emburse Spend API
Emburse Accounts API
Emburse Allocation API Controller V 1 API
Emburse Allocation API Controller V 2 API
Emburse Allocation API Controller V 3 API
Emburse Allowances API
Emburse Cards API
Emburse Categories API
Emburse Company API
Emburse Departments API
Emburse Entity Type API
Where this information came from

This is an independent, third-party profile of Emburse Shipping Addresses API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.