SDK setup

Configure each SDK with the same three ideas: client credentials, environment, and the application routes you want EndPointBlank to authorize and observe.

Ruby / Rails

end_point_blank_rails

Install the EndPointBlank package for this runtime, load credentials from environment variables, and enable request reporting around protected endpoints.

JavaScript

end_point_blank_js

Install the EndPointBlank package for this runtime, load credentials from environment variables, and enable request reporting around protected endpoints.

Python

end_point_blank_py

Install the EndPointBlank package for this runtime, load credentials from environment variables, and enable request reporting around protected endpoints.

Java

end_point_blank_java

Install the EndPointBlank package for this runtime, load credentials from environment variables, and enable request reporting around protected endpoints.

Elixir

end_point_blank_elixir

Install the EndPointBlank package for this runtime, load credentials from environment variables, and enable request reporting around protected endpoints.

ENDPOINTBLANK_CLIENT_ID=ijXI+MVwmrC5xH/9ZuGiQlAbAyobTqMa
ENDPOINTBLANK_CLIENT_SECRET=Bwq7lfupEfk5TsF30Z5YfeGd7WI3mhyiqOKysgR/QBCJknxeypY4ber79lPKaY5U
ENDPOINTBLANK_ENV=production
ENDPOINTBLANK_APP_NAME=Billing API

Pointing an SDK somewhere other than hosted EndPointBlank

Skip this if you use hosted EndPointBlank. The SDKs already default to https://in.endpointblank.com for authorization and https://log.endpointblank.com for logs, so there is nothing to set.

If you run your own intake, set both. They are separate hosts: overriding only the first leaves every request log still going to the hosted service.

ENDPOINTBLANK_BASE_URL=https://in.endpointblank.com
ENDPOINTBLANK_LOG_BASE_URL=https://log.endpointblank.com