API Endpoints
Url | Description |
|---|---|
https://ws.concordfax.com/fax/v5 | API endpoint that method calls will be executed against. |
https://ws.concordfax.com/fax/v5/faxws.wsdl | WSDL endpoint that describes API service. Used by many application frameworks to generate code proxies to service. |
https://login.concord.net/v1/connect/token | API endpoint to perform oauth authentication using Resource Owner Password Credentials (ROPC) Flow. This allows the exchange of username/password for a OAUTH Token that can be used to make API calls instead of supplying username/password to each API call. |
Concord’s Web Services and APIs provides multiple ways to authenticate an end user and client application. Depending on how your client application is built, it can use one or more of the authentication mechanisms supported by the Concord platform.
Authentication Styles
Username and Password | Concord's Web Services / APIs supports authentication using a username and password. Every request submitted to the API includes the username and password. |
OAuth 2.0 (Token Authentication) | This involves an end user authenticating against Concord’s Identity Server and receiving security tokens in return. These tokens are then used by the client application to interact with Concord’s APIs and Web Services and gain access. Several of these methods support both interactive and non-interactive authentication and authorization. Interactive means that the user can be prompted for input. For example, prompting the user to login, perform multi-factor authentication (MFA), or to grant additional consent to resources. Non-interactive, or silent, authentication attempts to acquire authentication without any direct user interaction. |
Additional Information
Please refer to API Authentication for details.
