# Get Authorization URL Get Keeta merchant authorization link for merchant authorization process. > Merchants can click this link to complete the authorization process. The returned URL can be used to redirect merchants to Keeta's authorization page. URL Example: "https://merchant.mykeeta.com/m/web/openapi/authorize?locale=en®ion=BR&cityId=110200008&risk_cost_id=&responseType=client_credentials&appId=2123830428&redirectUri=&state=&scope=all/#/app-activation" If Software Services wants merchants to be redirected to your own page after authorization, you can set the parameter accordingly. When the merchant completes authorization, they will be redirected to your specified with the following parameters appended: - : Unique authorization identifier for this specific authorization session. Use this ID for subsequent API calls. - : State parameter for request/response correlation (matches your original request) - : Your application identifier - : Authorization completion timestamp For detailed workflow, please refer to: Merchant Self-serve Authorization" HOST: DIRECTION: Endpoint: GET /oauth/authorization/url Version: v.1.0.6 ## Query parameters: - `clientId` (string, required) Client ID ## Response 200 fields (application/json): - `merchantAuthorizationUrl` (string, required) Authorization URL for merchant Example: "https://merchant.mykeeta.com/m/web/openapi/authorize?locale=en®ion=BR&cityId=110200008&risk_cost_id=&responseType=client_credentials&appId=2123830428&redirectUri=&state=&scope=all/#/app-activation" ## Response 401 fields (application/problem+json): - `title` (string, required) Short description of the problem. Example: "Unexpected error" - `status` (integer, required) HTTP code of the returned status. Example: 500 ## Response 503 fields (application/problem+json): - `title` (string, required) Short description of the problem. Example: "Unexpected error" - `status` (integer, required) HTTP code of the returned status. Example: 500