Raley PO exposes HTTP REST endpoints which you can use to facilitate B2B integration with your own system(s).
Authorization
The authorization is implemented via HTTP header "Authorization". Every time you execute a method call on our API you have to provide a valid value in this header.
To get the value of Authorization header, navigate to Raley Apps configuration page and then click on API & Integrations tab. Then copy the value from API Key and use in in your application(s) to retrieve and modify data in Raley PO.
You can always regenerate the Auhtorization header, however, make sure that you've updated your systems which are making use of it.
Available APIs
The following table lists available REST API methods that a third party service can invoke. URL's must start with https://po.raleyapps.com/ and end with the URL suffix as indicated in the table below
| Method | URL suffix | Descripction | Example Response |
|---|---|---|---|
| GET | api/v1/external/get-suppliers | Returns list of suppliers configured for given installation of Raley PO. Archived suppliers are not returned | [ |
| GET | api/v1/external/get-taxes | Returns list of taxes configured for given installation of Raley PO. Archived taxes are not returned | [ |
| GET | api/v1/external/find-products-by-sku?sku=SKU_VALUE | Finds and returns list of product that match by given SKU identifier SKU_VALUE. Both, active and archived products can be returned. This methods returns HTTP 404 if no products are found. | [ |
| POST | api/v1/external/create-product | Creates a product with given parameters passed as JSON array. sku - business identifier used to identify products in your system unitPrice - product price including applicable taxRate supplierId - id of supplier that offers this product taxRate - object containing an "id" field which corresponds to applicable tax rate active - whether the product should be active or archived approved - true when you're not using product approval process. Otherwise false. productApprovalType - null if you're not using the product approval process, otherwise a JSON object with mandatory "id" field which corresponds to the product approval type ID. On successful invocation, the method will return newly created product data in JSON format. | { |
| PUT | api/v1/external/update-product | Updates a product with given id to the values set in product fields. If the product specified by id is not found then this method will return HTTP 404 The semantic of he fields is the same as in create-product method. On successful invocation, the method will return updated product data in JSON format | { |
| POST | api/v1/external/create-supplier | Creates a supplier with specified fields. On successful invocation this method return created supplier in JSON format | {
|
| PUT | api/v1/external/update-supplier | Updates supplier with specified fields. If the supplier specified by id was not found then this method returns HTTP 404 On successful invocation this method return updated supplier in JSON format | {
|
| GET | api/v1/external/order-data?issueKey=MY_ISSUE_KEY | Retrieves a purchase order identifiable by Jira key MY_ISSUE_KEY. If purchase order is not found, this method returns HTTP 404 | {
|
