EasyPost Documentation (Preview)
The EasyPost API enables automated, authenticated document uploads to Bing's communication services. It supports single or batch uploads with metadata, which can be provided or extracted automatically from documents. Once uploaded, Bing systems validate, process, print, and lodge your mail.
This connector is available in the following products and regions:
| Service | Class | Regions |
|---|---|---|
| Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
| Contact | |
|---|---|
| Name | Bing Support |
| URL | https://help.bingmail.com.au/ |
| support@bing.com |
| Connector Metadata | |
|---|---|
| Publisher | Bing Technologies |
| API Documentation | https://docs.microsoft.com/connectors/easypostdocumentatio |
| Website | https://www.bingmail.com.au/ |
| Privacy policy | https://bingmail.com.au/privacy-policy |
| Categories | IT Operations |
Bing EasyPost Connector
The EasyPost API provides automated direct upload of documents to Bing's communication services. The API establishes an authenticated session allowing upload of a document or set of documents and associated metadata. After completing the session the Bing backed systems will validate, process, print and lodge your mail. Addressing information is provided to the API via a metadata file or alternatively, the auto processor can extract address and other metadata from within the documents.
Publisher
This connector is managed and published by Bing Technologies Pty Ltd
Prerequisites
To use the EasyPost Connector you'll need:
- A Microsoft Power Apps or Power Automate plan
- A Bing customer account
- A Bing portal user account and password
Supported Operations
The connector supports the following operations:
Get session ID: Obtain the session ID Using the Bing account code and the attached Basic Auth connection, a session ID is requested. This uses a HTTP GET request to "publicinterface/get_session_id.json". This will return a session ID (EPID) in JSON format.Upload files: Upload metadata and document Using a supplied session ID, a URL is constructed for uploading the file(s) using the HTTP PUT request. Multiple files can be uploaded in the session by using as many Upload files steps as necessary.End session: Terminate the session End the session with another HTTP GET request to the "publicinterface/end_session.json" endpoint with the session ID provided. This will return a status and list of the files that were successfully received. It will then trigger the back-end processing of the uploaded resources. Submitted letter(s) will appear in the Bing customer portal, identifiable by their Session ID.
Typical example:
graph LR
A["Get Session ID"]
A --> B["Upload files"]
B --> C["End session"]
Authentication
This connector only supports Basic Access Authentication. The prompt to create a connection using valid Bing credentials will present itself when adding this connector as a new step for the first time.
Known Issues and Limitations
| Item | Description |
|---|---|
| Digest Auth | Digest authentication is supported (and preferred) for this API, however Power Automate custom connectors don't currently support Digest Authentication out-of-the-box. |
| multipart/form-data | Another method of direct uploading files to the EasyPost system is the Multipart form method, however Power Automate custom connectors don't currently support this. |
| End session 200 OK | When using the End session action, if providing an invalid session ID the system will return 200 OK but with a body of: "error": "unknown session" |
Throttling Limits
| Name | Calls | Renewal Period |
|---|---|---|
| API calls per connection | 100 | 60 seconds |
Actions
| End session |
End a valid session, completing the upload to begin printing or sending. |
| Get session ID |
Get a valid session ID to begin uploading files |
| Upload files |
Upload a single file using a valid session ID |
End session
End a valid session, completing the upload to begin printing or sending.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Session ID
|
session_id | True | string |
The session ID for the session you wish to terminate. |
Returns
| Name | Path | Type | Description |
|---|---|---|---|
|
|
session_id | string |
The ended session ID |
|
|
result | string |
Final result of session (OK, NO FILES, etc..) |
|
status
|
status | string | |
|
files
|
files | array of object | |
|
|
files.name | string |
Uploaded filename |
|
|
files.sz | integer |
Size of uploaded file |
|
upld_sz
|
files.upld_sz | integer | |
|
cl_sz
|
files.cl_sz | integer | |
|
chunks
|
files.chunks | integer | |
|
intent
|
files.intent | integer | |
|
first
|
files.first | double | |
|
last
|
files.last | double | |
|
|
files.host | string |
Internal host handling request |
|
apath
|
files.apath | string | |
|
gpath
|
files.gpath | string | |
|
sha1
|
files.sha1 | string | |
|
error
|
error | string |
Request failed, usually unknown session. |
|
errs
|
errs | array of string |
Get session ID
Get a valid session ID to begin uploading files
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Bing account code
|
account | True | string |
The Bing account code associated with the request. |
Returns
| Name | Path | Type | Description |
|---|---|---|---|
|
user
|
user | string |
The username associated with the request. |
|
account
|
account | string |
The Bing account code associated with the request. |
|
session_id
|
session_id | string |
The created session ID |
Upload files
Upload a single file using a valid session ID
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Session ID
|
session_id | True | string |
The session ID to upload files to |
|
Filename
|
file_name | True | string |
The name of the file (incl file extention) |
|
File content
|
fileContent | True | binary |