1Forge Finance APIs

La estandarización de la conexión con cualquier banco en tiempo real.

Afterbanks API

ApiDapp

Introduction The Business Registries API is built on HTTP. The API is RESTful. It has predictable resource URIs. The API is documented in OpenAPI format. In addition to the standard OpenAPI syntax we use a few vendor extensions. Overview The following sections describe the resources that make up the Business Registries REST API. Current Version By default, all requests to https://api.abr.ato.gov.au receive the v1 version of the REST API. We encourage you to explicitly request this version via the Accept header. Accept: application/vnd.abr-ato.v1+json Schema All API access is over HTTPS, and accessed from https://api.abr.ato.gov.au. All data is sent and received as JSON. Blank fields are included. All dates use the ISO 8601 format: YYYY-MM-DD For example: 2017-07-01 (the 1st of July 2017) All timestamps use the ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ For example: 2017-07-01T11:05:06+10:00 Timezones Some requests allow for specifying timestamps or generate timestamps with time zone information. We apply the following rules, in order of priority, to determine timezone information for API calls. Explicitly provide an ISO 8601 timestamp with timezone information For API calls that allow for a timestamp to be specified, we use that exact timestamp. For example: 2017-07-01T11:05:06+10:00 Pagination Information about pagination is provided in the Link header. For example: Link:; rel="next",; rel="last" rel="next" states that the next page is page=2. This makes sense, since by default, all paginated queries start at page 1. rel="last" provides some more information, stating that the last page of results is on page 34. Accordingly, we have 33 more pages of information that we can consume. Parameters Many API methods take optional parameters: GET /individuals/1234/addresses/?addressType='Mailing' In this example, the '1234' value is provided for the :partyId parameter in the path while :addressType is passed in the query string. For POST, PATCH, PUT, and DELETE requests, parameters not included in the URL should be encoded as JSON with a Content-Type of 'application/json'. Metadata The API provides metadata services that you can use to discover information about the classifcation schemes and values used by the Registry. For example: GET /classifications/roles Sample response: [ { "id": "123e4567-e89b-12d3-a456-426655440001", "role": "Director", "roleDescription": "An individual responsible for managing a company's ...", "relationship": "Directorship", "reciprocalRole": "Company", "reciprocalRoleDescription": "An incorporated legal entity." }, { ... } ] Root Endpoint You can issue a GET request to the root endpoint (also known as the service root) to get all the endpoint categories that the REST API supports: curl https://api.abr.ato.gov.au Authentication The Business Registries API supports API Key authentication. When you sign up for an account, you are given your first API key. You can generate additional API keys, and delete API keys (as you may need to rotate your keys in the future). You authenticate to the Business Registries API by providing your secret key in the request header. Note: Some requests will return 404 Not Found, instead of 403 Permission Denied. This is to prevent the accidental leakage of information to unauthorised users.

Business Registries

Beanstream Payments

Welcome to the Big Red Cloud API This API enables programmatic access to Big Red Cloud data. We have used Swagger to auto generate the API documentation on this page, and it also enables direct interaction with the API in this page. To get started, you will require an API Key - check out our guide at https://www.bigredcloud.com/support/generating-api-key-guide/ for information on how to get one. Use the 'Enter API Key' button below to enter your API key and start interacting with your Big Red Cloud data right on this page. The API key will be stored in your browsers local storage for convenience, but you will be able to delete it at any time if you wish. For additional information on the API, check out our support article at https://www.bigredcloud.com/support/api/

Big Red Cloud API

This is a Billingo API v3 documentation. Our API based on REST software architectural style. API has resource-oriented URLs, accepts JSON-encoded request bodies and returns JSON-encoded responses. To use this API you have to generate a new API key on our site. After that, you can test your API key on this page.

Billingo API v3

BIN lookup API, the free api service from bintable.com to lookup card information using it's BIN. the service maintains updated database based on the comunity and other third party services to make sure all BINs in the database are accurate and up to date.

BIN Lookup API

API Interface to retrieve company data and products from business registers

KYC API Documentation

bunq API

Chaingateway.io REST API to build the bridge between Ethereum and the real world Please check out our website for detailed information about this API. To use our API, you need an API Key (Described as Authorization header in the examples below). To get one, please create an account on our website. For our internal documentation, please check out our Docs Site. If you need help with integrating our API in your application, you can reach us via email or join our official Telegram group.

Chaingateway.io

Cnab Online

Learn more about home mortgage data, download the data yourself, or build new tools using our API.

The Consumer Financial Protection Bureau

Run in Postman or View Postman docs Quickstart Visit github to view the quickstart tutorial. Tutorial for running the API in postman Click on ""Run in Postman"" button postman - tutorial - 1 --- A new page will open. Click the ""Postman for windows"" to run postman as a desktop app. Make sure you have already installed Postman. postman - tutorial - 2 --- In chrome an alert might show up to set a default app for opening postman links. Click on ""Open Postman"". postman - tutorial - 3 --- The OpenAPI specification will be imported in Postman as a new collection named ""Envoice api"" postman - tutorial - 4 --- When testing be sure to check and modify the environment variables to suit your api key and secret. The domain is set to envoice's endpoint so you don't really need to change that. \*Eye button in top right corner postman - tutorial - 5 postman - tutorial - 6 --- You don't need to change the values of the header parameters, because they will be replaced automatically when you send a request with real values from the environment configured in the previous step. postman - tutorial - 7 --- Modify the example data to suit your needs and send a request. postman - tutorial - 8 Webhooks Webhooks allow you to build or set up Envoice Apps which subscribe to invoice activities. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external invoice data storage. In order to use webhooks visit this link and add upto 10 webhook urls that will return status 200 in order to signal that the webhook is working. All nonworking webhooks will be ignored after a certain period of time and several retry attempts. If after several attempts the webhook starts to work, we will send you all activities, both past and present, in chronological order. The payload of the webhook is in format:

API v1.0.0

Fetch the latest currency exchange rates via API. ExchangeRate-API is free and unlimited.

ExchangeRate-API

The fire.com API allows you to deeply integrate Business Account features into your application or back-office systems. The API provides read access to your profile, accounts and transactions, event-driven notifications of activity on the account and payment initiation via batches. Each feature has its own HTTP endpoint and every endpoint has its own permission. The API exposes 3 main areas of functionality: financial functions, service information and service configuration. Financial Functions These functions provide access to your account details, transactions, payee accounts, payment initiation etc. Service Functions These provide information about the fees and limits applied to your account. Service configuration These provide information about your service configs - applications, webhooks, API tokens, etc.

Fire Financial Services Business API

This API allows developers to integrate the Frankie Financial Compliance Utility into their applications. The API allows: Checking name, address, date of birth against national databases Validating Australian driver's licences, passports, medicare, visas and other Australian national ID documents Validating Australian electricity bills Validating NZ driver's licences Validating Chinese bank cards and national ID card Validating International passports and national ID documents PEP, Sanctions, Watchlist and adverse media checking Australian visa checks Fraud list and fraud background checks ID validation and selfie check comparisons. Industry specific services Comparing Australian electricity retailers for a better deal. KYB specific services Query organisation ownership Perform KYC & AML checks on shareholders, beneficial owners and office bearers. Query credit score and credit reports International company searches International company profiles The full version of this documentation along with supplemental articles can be found here: https://apidocs.frankiefinancial.com/ The traditional Swagger view of this documentation can be found here: https://app.swaggerhub.com/apis-docs/FrankieFinancial/kycutility Sandbox base URL is: https://api.demo.frankiefinancial.io/compliance/v1.2 We do have an old sandbox at https://sandbox.frankiefinancial.com/compliance/v1.2 but this has been retired. All calls are the same as production, only with canned data. Full Swagger definition, along with test data for playing in the sandbox can be obtained once initial commercial discussions have commenced. Production and optional UAT access will be opened up only to those with a signed commercial contract. Contact us at hello@frankiefinancial.com to speak with a sales rep about issuing a Customer ID and Sandbox api key.

Frankie Financial API

ATM Locator API

Branch Locator API

Product Finder API

Interactive Brokers Web API for 3rd Party Companies

IBKR 3rd Party Web API

Reimbursements API

Authentication is required to access all methods of the API. Enter username and password. Credentials are automatically set as you type.

Tradeworks

An API for accessing the NaviPlan Fact Finder.

Advicent.FactFinderService

An API for accessing NaviPlan plan data for a client.

NaviPlan API

Account and Transaction API Specification - UK

nFusion Solutions provides REST APIs that deliver enterprise-grade financial data. Data sets include real-time and historical pricing for Spot prices of precious metals such as Gold, Silver, Platinum, and Palladium, exchange rates for major currency pairs, exchange rates for Crypto Currencies such as BTC, ETH, and LTC. All API access requires authentication. In order to be issued access credentials you must first enter into a service agreement with nFusion Solutions and acquire a commercial license. For information on how to obtain a licence take a tour of our products or email sales@nfusionsolutions.com.

nFusion Solutions Market Data API v1

Nordigen Account Information Services API

NOWPayments is a non-custodial cryptocurrency payment processing platform. Accept payments in a wide range of cryptos and get them instantly converted into a coin of your choice and sent to your wallet. Keeping it simple – no excess. Sandbox Before production usage, you can test our API using the Sandbox. Details can be found here Authentication To use the NOWPayments API you should do the following: Sign up at nowpayments.io Specify your outcome wallet Generate an API key Standard e-commerce flow for NOWPayments API: API - Check API availability with the "GET API status" method. If required, check the list of available payment currencies with the "GET available currencies" method. UI - Ask a customer to select item/items for purchase to determine the total sum; UI - Ask a customer to select payment currency API - Get the minimum payment amount for the selected currency pair (payment currency to your Outcome Wallet currency) with the "GET Minimum payment amount" method; API - Get the estimate of the total amount in crypto with "GET Estimated price" and check that it is larger than the minimum payment amount from step 4; API - Call the "POST Create payment" method to create a payment and get the deposit address (in our example, the generated BTC wallet address is returned from this method); UI - Ask a customer to send the payment to the generated deposit address (in our example, user has to send BTC coins); UI - A customer sends coins, NOWPayments processes and exchanges them (if required), and settles the payment to your Outcome Wallet (in our example, to your ETH address); API - You can get the payment status either via our IPN callbacks or manually, using "GET Payment Status" and display it to a customer so that they know when their payment has been processed. API - you call the list of payments made to your account via the "GET List of payments" method. Additionally, you can see all of this information in your Account on NOWPayments website. Alternative flow API - Check API availability with the "GET API status" method. If required, check the list of available payment currencies with the "GET available currencies" method. UI - Ask a customer to select item/items for purchase to determine the total sum; UI - Ask a customer to select payment currency API - Get the minimum payment amount for the selected currency pair (payment currency to your Outcome Wallet currency) with the "GET Minimum payment amount" method; API - Get the estimate of the total amount in crypto with "GET Estimated price" and check that it is larger than the minimum payment amount from step 4; API - Call the "POST Create Invoice method to create an invoice. Set "success_url" - parameter so that the user will be redirected to your website after successful payment. UI - display the invoice url or redirect the user to the generated link. NOWPayments - the customer completes the payment and is redirected back to your website (only if "success_url" parameter is configured correctly!). API - You can get the payment status either via our IPN callbacks or manually, using "GET Payment Status" and display it to a customer so that they know when their payment has been processed. API - you call the list of payments made to your account via the "GET List of payments" method. Additionally, you can see all of this information in your Account on NOWPayments website. API Documentation Instant Payments Notifications IPN (Instant payment notifications, or callbacks) are used to notify you when transaction status is changed. To use them, you should complete the following steps: Generate and save the IPN Secret key in Store Settings tab at the Dashboard. Insert your URL address where you want to get callbacks in createpayment request. The parameter name is ipn\callback\_url. You will receive payment updates (statuses) to this URL address. You will receive all the parameters at the URL address you specified in (2) by POST request. The POST request will contain the x-nowpayments-sig parameter in the header. The body of the request is similiar to a get payment status response body. Example: {"paymentid":5077125051,"paymentstatus":"waiting","payaddress":"0xd1cDE08A07cD25adEbEd35c3867a59228C09B606","priceamount":170,"pricecurrency":"usd","payamount":155.38559757,"actuallypaid":0,"paycurrency":"mana","orderid":"2","orderdescription":"Apple Macbook Pro 2019 x 1","purchaseid":"6084744717","createdat":"2021-04-12T14:22:54.942Z","updatedat":"2021-04-12T14:23:06.244Z","outcomeamount":1131.7812095,"outcome_currency":"trx"} Sort all the parameters from the POST request in alphabetical order. Convert them to string using JSON.stringify (params, Object.keys(params).sort()) or the same function. Sign a string with an IPN-secret key with HMAC and sha-512 key Compare the signed string from the previous step with the x-nowpayments-sig , which is stored in the header of the callback request. If these strings are similar it is a success. Otherwise, contact us on support@nowpayments.io to solve the problem. Example of creating a signed string at Node.JS const hmac = crypto.createHmac('sha512', notificationsKey); hmac.update(JSON.stringify(params, Object.keys(params).sort())); const signature = hmac.digest('hex'); Example of comparing signed strings in PHP function checkipnrequestisvalid() { $error_msg = "Unknown error"; $auth_ok = false; $request_data = null; if (isset($SERVER['HTTPXNOWPAYMENTSSIG']) && !empty($SERVER['HTTPXNOWPAYMENTSSIG'])) { $recivedhmac = $SERVER['HTTPXNOWPAYMENTS_SIG']; $requestjson = fileget_contents('php://input'); $requestdata = jsondecode($request_json, true); ksort($request_data); $sortedrequestjson = jsonencode($requestdata); if ($requestjson !== false && !empty($requestjson)) { $hmac = hashhmac("sha512", $sortedrequestjson, trim($this->ipnsecret)); if ($hmac == $recived_hmac) { $auth_ok = true; } else { $error_msg = 'HMAC signature does not match'; } } else { $error_msg = 'Error reading POST data'; } } else { $error_msg = 'No HMAC signature sent.'; } } Recurrent payment notifications If an error is detected, the payment is flagged and will receive additional recurrent notifications (number of recurrent notifications can be changed in your Store Settings-> Instant Payment Notifications). If an error is received again during processing of the payment, recurrent notifications will be initiated again. Example: "Timeout" is set to 1 minute and "Number of recurrent notifications" is set to 3. Once an error is detected, you will receive 3 notifications at 1 minute intervals. Several payments for one order If you want to create several payments for one Order you should do the following: Create a payment for the full order amount. Save "purchaseid" which will be in "createpayment" response Create next payment or payments with this "purchaseid" in "createpayment" request. Only works for partially_paid payments It may be useful if you want to give your customers opportunity to pay a full order with several payments, for example, one part in BTC and one part in ETH. Also, if your customer accidentally paid you only part of a full amount, you can automatically ask them to make another payment. Packages Please find our out-of-the box packages for easy integration below: JavaScript package More coming soon! Payments

NOWPayments API

Ntropy Transaction API for transaction classification & management Contact Support: Name: API Support Email: api@ntropy.network

Ntropy Transaction API

Latest Swagger specification for OpenData

Open Data API

Swagger for Account and Transaction API Specification

Account and Transaction API Specification

Swagger for Confirmation of Funds API Specification

Confirmation of Funds API Specification

Swagger for Event Notification API Specification - TPP Endpoints

Event Notification API Specification - TPP Endpoints

Swagger for Payment Initiation API Specification

Payment Initiation API

Summary The Swiss NextGen API is based on the NextGenPSD2 Framework Version 1.3.4 of the Berlin Group which offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGen Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The Swiss edtion refines the message formats specific to Switzerland and defines some matching examples. The possible Approaches are: Redirect SCA Approach (Not recommended by obp.ch community) OAuth SCA Approach (Not recommended by obp.ch community) Decoupled SCA Approach (Not recommended by obp.ch community) Embedded SCA Approach without SCA method (Not recommended by obp.ch community) Embedded SCA Approach with only one SCA method available (Not recommended by obp.ch community) Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional Therefore for a particular implementation of a compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** Some General Remarks Related to this version of the OpenAPI Specification: This API definition is based on the Implementation Guidelines of the Berlin Group API. It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group API. This API definition contains the REST-API for requests from the PISP to the ASPSP. This API definition contains the messages for all different approaches defined in the Implementation Guidelines. According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a comlient API in addition to the elements defined in this file. General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the API have to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space

Swiss NextGen Banking API-Framework

Introduction OpenFinTech.io is an open database that comprises of standardized primary data for FinTech industry. It contains such information as geolocation data (countries, cities, regions), organizations, currencies (national, digital, virtual, crypto), banks, digital exchangers, payment providers (PSP), payment methods, etc. It is created for communication of cross-integrated micro-services on "one language". This is achieved through standardization of entity identifiers that are used to exchange information among different services. UML UML Domain Model diagram you can find here. Persistence Entities are updated not more than 1 time per day. Terms and Conditions This OpenFinTech.io is made available under the Open Database License. Any rights in individual contents of the database are licensed under the Database Contents License. Contacts For any questions, please email - info@openfintech.io Or you can contact us at Gitter Powered by Paymaxi Get Started If you use POSTMAN or similar program which can operate with swagger`s files - just download our spec and import it. Also you can try live API demo. Overview The OpenFinTech API is organized around REST. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. API is based on JSON API standard. JSON is returned by all API responses, including errors, although our API libraries convert responses to appropriate language-specific objects. JSON API requires use of the JSON API media type (application/vnd.api+json) for exchanging data. Additional Request Headers ACCEPT HEADER Your requests should always include the header: If argument height or width is missing API returns original image with real sizes. Errors API uses conventional HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, etc.), and codes in the 5xx range indicate an error with OpenFinTech's servers (these are rare). | Code | Description | |------|-------------| | 200 - OK	| Everything worked as expected. | | 400 - Bad Request |	The request was unacceptable, often due to missing a required parameter. | | 401 - Unauthorized |	No valid API key provided. | | 402 - Request Failed	| The parameters were valid but the request failed. | | 404 - Not Found |	The requested resource doesn't exist. | | 409 - Conflict	| The request conflicts with another request (perhaps due to using the same idempotent key). | | 429 - Too Many Requests |	Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. | | 500, 502, 503, 504 - Server Errors |	Something went wrong on OpenFinTech's end. (These are rare.) |

OpenFinTech.io

For general questions and support of the API, contact: webservices@paylocity.com Overview Paylocity Web Services API is an externally facing RESTful Internet protocol. The Paylocity API uses HTTP verbs and a RESTful endpoint structure. OAuth 2.0 is used as the API Authorization framework. Request and response payloads are formatted as JSON. Paylocity supports v1 and v2 versions of its API endpoints. v1, while supported, won't be enhanced with additional functionality. For direct link to v1 documentation, please click here. For additional resources regarding v1/v2 differences and conversion path, please contact webservices@paylocity.com. Setup Paylocity will provide the secure client credentials and set up the scope (type of requests and allowed company numbers). You will receive the unique client id, secret, and Paylocity public key for the data encryption. The secret will expire in 365 days. Paylocity will send you an e-mail 10 days prior to the expiration date for the current secret. If not renewed, the second e-mail notification will be sent 5 days prior to secret's expiration. Each email will contain the code necessary to renew the client secret. You can obtain the new secret by calling API endpoint using your current not yet expired credentials and the code that was sent with the notification email. For details on API endpoint, please see Client Credentials section. Both the current secret value and the new secret value will be recognized during the transition period. After the current secret expires, you must use the new secret. If you were unable to renew the secret via API endpoint, you can still contact Service and they will email you new secret via secure email. When validating the request, Paylocity API will honor the defaults and required fields set up for the company default New Hire Template as defined in Web Pay. Authorization Paylocity Web Services API uses OAuth2.0 Authentication with JSON Message Format. All requests of the Paylocity Web Services API require a bearer token which can be obtained by authenticating the client with the Paylocity Web Services API via OAuth 2.0. The client must request a bearer token from the authorization endpoint: auth-server for production: https://api.paylocity.com/IdentityServer/connect/token auth-server for testing: https://apisandbox.paylocity.com/IdentityServer/connect/token Paylocity reserves the right to impose rate limits on the number of calls made to our APIs. Changes to API features/functionality may be made at anytime with or without prior notice. Authorization Header The request is expected to be in the form of a basic authentication request, with the "Authorization" header containing the client-id and client-secret. This means the standard base-64 encoded user:password, prefixed with "Basic" as the value for the Authorization header, where user is the client-id and password is the client-secret. Content-Type Header The "Content-Type" header is required to be "application/x-www-form-urlencoded". Additional Values The request must post the following form encoded values within the request body: granttype = clientcredentials scope = WebLinkAPI Responses Success will return HTTP 200 OK with JSON content: { "access_token": "xxx", "expires_in": 3600, "token_type": "Bearer" } Encryption Paylocity uses a combination of RSA and AES cryptography. As part of the setup, each client is issued a public RSA key. Paylocity recommends the encryption of the incoming requests as additional protection of the sensitive data. Clients can opt-out of the encryption during the initial setup process. Opt-out will allow Paylocity to process unencrypted requests. The Paylocity Public Key has the following properties: 2048 bit key size PKCS1 key format PEM encoding Properties key (base 64 encoded): The AES symmetric key encrypted with the Paylocity Public Key. It is the key used to encrypt the content. Paylocity will decrypt the AES key using RSA decryption and use it to decrypt the content. iv (base 64 encoded): The AES IV (Initialization Vector) used when encrypting the content. content (base 64 encoded): The AES encrypted request. The key and iv provided in the secureContent request are used by Paylocity for decryption of the content. We suggest using the following for the AES: CBC cipher mode PKCS7 padding 128 bit block size 256 bit key size Encryption Flow Generate the unencrypted JSON payload to POST/PUT Encrypt this JSON payload using your own key and IV (NOT with the Paylocity public key) RSA encrypt the key you used in step 2 with the Paylocity Public Key, then, base64 encode the result Base64 encode the IV used to encrypt the JSON payload in step 2 Put together a "securecontent" JSON object: { 'secureContent' : { 'key' : -- RSA-encrypted & base64 encoded key from step 3, 'iv' : -- base64 encoded iv from step 4 'content' -- content encrypted with your own key from step 2, base64 encoded } } Sample Example { "secureContent": { "key": "eS3aw6H/qzHMJ00gSi6gQ3xa08DPMazk8BFY96Pd99ODA==", "iv": "NLyXMGq9svw0XO5aI9BzWw==", "content": "gAEOiQltO1w+LzGUoIK8FiYbU42hug94EasSl7N+Q1w=" } } Sample C# Code using Newtonsoft.Json; using System; using System.IO; using System.Security.Cryptography; using System.Text; public class SecuredContent { [JsonProperty("key")] public string Key { get; set; } [JsonProperty("iv")] public string Iv { get; set; } [JsonProperty("content")] public string Content { get; set; } } public class EndUserSecureRequestExample { public string CreateSecuredRequest(FileInfo paylocityPublicKey, string unsecuredJsonRequest) { string publicKeyXml = File.ReadAllText(paylocityPublicKey.FullName, Encoding.UTF8); SecuredContent secureContent = this.CreateSecuredContent(publicKeyXml, unsecuredJsonRequest); string secureRequest = JsonConvert.SerializeObject(new { secureContent }); return secureRequest; } private SecuredContent CreateSecuredContent(string publicKeyXml, string request) { using (AesCryptoServiceProvider aesCsp = new AesCryptoServiceProvider()) { aesCsp.Mode = CipherMode.CBC; aesCsp.Padding = PaddingMode.PKCS7; aesCsp.BlockSize = 128; aesCsp.KeySize = 256; using (ICryptoTransform crt = aesCsp.CreateEncryptor(aesCsp.Key, aesCsp.IV)) { using (MemoryStream outputStream = new MemoryStream()) { using (CryptoStream encryptStream = new CryptoStream(outputStream, crt, CryptoStreamMode.Write)) { byte[] encodedRequest = Encoding.UTF8.GetBytes(request); encryptStream.Write(encodedRequest, 0, encodedRequest.Length); encryptStream.FlushFinalBlock(); byte[] encryptedRequest = outputStream.ToArray(); using (RSACryptoServiceProvider crp = new RSACryptoServiceProvider()) { crp.FromXmlstring(publicKeyXml); byte[] encryptedKey = crp.Encrypt(aesCsp.Key, false); return new SecuredContent() { Key = Convert.ToBase64string(encryptedKey), Iv = Convert.ToBase64string(aesCsp.IV), Content = Convert.ToBase64string(encryptedRequest) }; } } } } } } } Support Questions about using the Paylocity API? Please contact webservices@paylocity.com. Deductions (v1) Deductions API provides endpoints to retrieve, add, update and delete deductions for a company's employees. For schema details, click here. OnBoarding (v1) Onboarding API sends employee data into Paylocity Onboarding to help ensure an easy and accurate hiring process for subsequent completion into Web Pay. For schema details, click here.

Paylocity API

GOV.UK Pay API (This version is no longer maintained. See openapi/publicapi_spec.json for latest API specification)

GOV.UK Pay API

Open, scableable, transparent payroll API.

PayRun.IO

The Plaid REST API. Please see https://plaid.com/docs/api for more details.

The Plaid API

PocketSmith

Polygon

Portfolio Optimizer is a Web API to optimize the composition of investment portfolios (collection of financial assets such as stocks, bonds, ETFs, crypto-currencies) using modern portfolio theory-like algorithms (mean-variance, etc.). API General Information Portfolio Optimizer is based on REST for easy integration, uses JSON for the exchange of data and uses the two most common HTTP verbs (GET, POST) to represent the actions. Portfolio Optimizer is also as secured as a Web API could be: 256-bit HTTPS Encryption No usage of cookies No usage of personal data API Headers The following HTTP header(s) are required when calling Portfolio Optimizer endpoints: Content-type: application/json This header specifies that the data provided in input to the endpoint is in JSON format The following HTTP header(s) are optional when calling Portfolio Optimizer endpoints: X-API-Key: This header enables authenticated users to provide their private API key in order to benefit from higher API limits API Key Portfolio Optimizer is free to use, but not free to run. In order to obtain an API key and benefit from higher API limits, a small participation to Portfolio Optimizer running costs is required. This participation takes the form of coffee(s), with one coffee = one month of usage. Notes: > * Please make sure not to expose your API key publicly! API Limits Portfolio Optimizer comes with fairly reasonable API limits. For anonymous users: The API requests are restricted to a subset of all the available endpoints and/or endpoints features The API requests are limited to 1 request per second for all the anonymous users combined, with concurrent requests rejected The API requests are limited to 1 second of execution time The API requests are limited to 20 assets, 100 portfolios, 500 series data points and 5 factors For authenticated users with an API key: The API requests have access to all the available endpoints and endpoints features The API requests are limited to 10000 requests per 24 hour per API key, with concurrent requests queued The API requests are limited to 2.5 seconds of execution time The API requests are limited to 100 assets, 500 portfolios, 2500 series data points and 25 factors > Notes: > * It is possible to further relax the API limits, or to disable the API limits alltogether; please contact the support for more details. > * Information on the API rate limits are provided in response messages HTTP headers x-ratelimit-*: > * x-ratelimit-limit-second, the limit on the number of API requests per second > * x-ratelimit-remaining-second, the number of remaining API requests in the current second > * x-ratelimit-limit-minute, the limit on the number of API requests per minute > * ... API Regions Portfolio Optimizer servers are located in Western Europe. > Notes: > * It is possible to deploy Portfolio Optimizer in other geographical regions, for example to improve the API latency; please contact the support for more details. API Response Codes Standard HTTP response codes are used by Portfolio Optimizer to provide details on the status of API requests. | HTTP Code | Description | Notes | | --------- | ----------- | ----- | | 200 | Request successfully processed | - | | 400 | Request failed to be processed because of incorrect content | The response message body contains information on the incorrect content | | 401 | Request failed to be processed because of invalid API key | - | | 404 | Request failed to be processed because of non existing endpoint | The requested endpoint might exist, but needs to be accessed with another HTTP method (e.g., POST instead of GET) | | 429 | Request failed to be processed because of API limits violated | The response message HTTP headers x-ratelimit-* contain information on the API limits | | 500 | Request failed to be processed because of an internal error | Something went wrong on Portfolio Optimizer side, do not hesitate to report the issue | | 502 | Request failed to be processed because of a temporary connectivity error | Something went wrong on Portfolio Optimizer side, please check the API status and do not hesitate to report the issue | API Status Portfolio Optimizer is monitored 24/7 by UptimeRobot. Support For any issue or question about Portfolio Optimizer, please do not hesitate to contact the support.

Portfolio Optimizer

Currency Authority: Exchange Rate of 1453 country currencies and crypto currencies

Sonar Trading

This is an API designed for merchants who are using SpectroCoin services and wishes to integrate them locally.

SpectroCoin Merchant

Storecove API

Introduction Taxrates.io is a global tax rate service that automates the management of monitoring tax rates changes in 181 countries. We monitor over 14,000 US sales tax, VAT, GST rates for you and make updates via our API so you always have the most update tax rates. You can use Taxrates.io as a virtual sandbox where we provide you with 30 days free trial. Countries We currently support the following countries around the world. If you would like to request the addition of a new country, please email us at support@taxrates.io Afghanistan Gambia Nicaragua Albania Georgia Niger Andorra Germany Nigeria Angola Ghana North Korea Antigua and Barbuda Greece Norway Argentina Grenada Pakistan Armenia Guam Palestine Aruba Guatemala Panama Australia Guinea Papua New Guinea Austria Guyana Paraguay Azerbaijan Haiti Peru Bahamas Honduras Philippines Bangladesh Hungary Poland Barbados Iceland Portugal Belarus India Puerto Rico Belgium Indonesia Republic of the Congo Belize Iran Romania Benin Ireland Russian Federation Bhutan Isle of Man Rwanda Bolivia Israel Samoa Bonaire Italy Senegal Bosnia and Herzegovina Japan Serbia Botswana Jersey Seychelles Brazil Jordan Sierra Leone Bulgaria Jordan Singapore Burkina Faso Kazakhstan Slovakia Burundi Kenya Slovenia Cambodia Kiribati Solomon Islands Cameroon Kosovo Somalia Cape Verde Kyrgyzstan South Africa Central African Republic Laos South Korea Chad Latvia South Sudan Chile Lebanon Spain China Lesotho Sri Lanka Columbia Liberia St Lucia Comoros Liechtenstein Sudan Cook Islands Lithuania Suriname Costa Rica Luxembourg Swaziland Cote d'Ivoire Macedonia Sweden Croatia Madagascar Switzerland Cuba Malawi Tahiti Curacao Malaysia Taiwan Cyprus Maldives Tajikistan Czech Republic Mali Tanzania Democratic Republic of the Congo Malta Thailand Denmark Mauritania Togo Djbouti Mauritius Tonga Dominica Mexico Trinidad and Tobago Dominican Republic Micronesia Tunisia Ecuador Moldova Turkmenistan Egypt Monaco Tuvalu El Salvador Mongolia Uganda Equatorial Guinea Montenegro Ukraine Eritrea Morocco United Kingdom Estonia Mozambique United States Ethiopia Myanmar Uruguay Fiji Namibia Vanuatu Finland Nepal Venezuela France Netherlands Vietnam Gabon New Zealand Yemen Products codes The Taxrates.io API’s provides product-level tax rates for a subset of product codes. These codes are to be used for products that are either exempt from tax in some jurisdictions or are taxed at reduced rates. We will be expanding support for additional, less common categories over time. If you would like to request the addition of a new product category, please email us at support@taxrates.io Please select a product code/s when making a request to the Taxrates.io API Product code Product Description C010 Services which are not subject to a service-specific tax C011 Software - Downloaded C012 Books - Downloaded C011 Music - Downloaded C011 Movies/Digital Video - Downloaded C011 Other Electronic Goods - Downloaded C011 Streaming Music/Audio Services new C011 Streaming Video Services new C018 Software as a Services, Generally (Remote Access to Hosted Software) C018 Remote Access to Hosted Software - Personal Use C018 Remote Access to Hosted Software - Business Use C021 Remote Access to Hosted Business Custom Applications C021 Personal Cloud Storage/Backup C021 Business Cloud Storage/Backup C021 Business Data Warehouses C022 Infrastructure as Service, Generally C022 Ecommerce Site/Webserver Hosting C022 Provision of Virtual Computing Capacity C022 Software - package or canned program C022 Software - modifications to canned program C022 Software - custom programs - material C022 Software - custom programs - professional serv. C022 Information services C022 Data processing services C022 Mainframe computer access and processing serv. C022 Online Data processing services Filtering When calling the API endpoints you can use 'filter' parameters to get tax rate for the selected type. You can get the following tax types (Each tax rate will always have one of following types) US Sales tax Rates CombinedRate StateRate CountyRate CityRate SpecialRate We recommend using Postman when discovering our API. Happy using! Rate Limiting We limit API requests. If you’re exceeding this rate and encountering 429 errors, review the following: Only make requests in states / regions where you have enabled. Cache responses if the order details haven’t changed since the last calculation at checkout. Errors The Taxrates.io API uses the following error codes: Code Error Message 400 Bad Request – Your request format is bad. 401 Unauthorized – Your API key is wrong. 404 Not Found – The specified resource could not be found. 405 Method Not Allowed – You tried to access a resource with an invalid method. 429 Too Many Requests – You’re requesting too many resources! Slow down! 500 Internal Server Error – We had a problem with our server. Try again later. 503 Service Unavailable – We’re temporarily offline for maintenance. Try again later. Verify your API token is correct and make sure you’re correctly setting the Authorization header. If you’re still not sure what’s wrong, contact us and we’ll investigate. Changelog Stay on top of new developer-facing features, accuracy improvements, and bug fixes for our API. Have a request? Encounter an issue? We’d love to hear your feedback. Contact Support: Name: apiteam@taxrates.io

Taxrates.io API

Overview Tradematic Cloud is a trading infrastructure for building investment services. It’s a trading engine + API + ready-made adapters to stock and forex brokers, crypto exchanges, and market data providers. You can use it as a cloud API, or you can deploy it on your servers. How to use Tradematic Cloud API Sign up at tradematic.cloud. After signing up, you will receive your API key. Authorization Add the 'X-API-KEY' header with your API key to each request. Examples of writing code with Tradematic Cloud API Examples are available at tradematic.cloud. Swagger (.yaml) File Swagger (.yaml) file can be found here.

Tradematic Cloud API

The Up API gives you programmatic access to your balances and transaction data. You can request past transactions or set up webhooks to receive real-time events when new transactions hit your account. It’s new, it’s exciting and it’s just the beginning.

Up API

A developer friendly API to help your business achieve VAT compliance

VAT API

Introduction The Xero Accounting API is a RESTful web service and uses the OAuth (v1.0a) protocol to authenticate 3rd party applications. The Accounting API exposes accounting and related functions of the main Xero application and can be used for a variety of purposes such as creating transactions like invoices and credit notes, right through to extracting accounting data via our reports endpoint.

Accounting

These endpoints are related to managing authentication tokens and identity for Xero API

Xero OAuth 2 Identity Service API

This is the Xero Payroll API for orgs in Australia region.

Xero Payroll AU API

Xero Accounting API

The Assets API exposes fixed asset related functions of the Xero Accounting application and can be used for a variety of purposes such as creating assets, retrieving asset valuations etc.

Xero Assets API

The Bank Feeds API is a closed API that is only available to financial institutions that have an established financial services partnership with Xero. If you're an existing financial services partner that wants access, contact your local Partner Manager. If you're a financial institution who wants to provide bank feeds to your business customers, contact us to become a financial services partner.

Xero Bank Feeds API

These endpoints are specific to Xero Files API

Xero Files API

Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body. API Documentation is at https://api.youneedabudget.com

Product

Applications

Learn

Tools

Misc

Financial APIs mock samples for your project