Authentication service for SW services using a username and password. It generates a temporary token, valid for two hours, that you can use to connect to SW services.
✓
Before you start
1
Request sandbox credentials through our form. For production, use the username and password of your SW account.
2
Choose your environment. Sandbox credentials don’t work in production, and vice versa.
3
Cache the token and renew it before it expires. Check
expires_in before each call; don’t request a new token for every stamping request.
💡 Recommendation: If you need a non-expiring token, you can get an infinite token assigned to your account from the Stamp Manager (Administrador de Timbres).
URLs
Select your active environment. The copy buttons and the code examples below are built with the base URL you choose here.
🔗 Endpoint
💡 Note: This is the only SW service that does not require an
Authorization header: this is where you get it.
Request Example
💡 Note: These examples are direct REST calls. The SW SDKs also handle authentication: check the repository for your language to find the exact method.
Response
This endpoint takes no path parameters. The path is fixed:
/v2/security/authenticate.In SW® we strive to be the best for You, which is why your opinion is very important. Please help us by rating this article and leaving your comments.