Repairy Partner API
    Repairy Partner API
    • Welcome 👋
    • Get Started
    • HTTP Headers
    • Authorization
    • Workshops
    • Bookings
    • Quotes
    • Service Reminder
    • Data Reporting
    • Booking URL
    • Error Codes
    • Technical Support
    • Changelog
    • Webhook
    • Additional Services
    • Service Catalog
    • APIs
      • Authorization
        • Access Token
        • Refresh Token
      • Workshops
        • Availabilities
        • Service Catalog
      • Bookings
        • Booking Request with Service Catalog (beta)
        • Booking Request
        • Booking Information
        • Update Booking Information
        • Update Booking Status
      • Quotes
        • Quote Request
      • Service Reminder
        • Service Reminder Notification
        • Service Reminder Information
      • Data Reporting
        • Partner Report
    • Data Structures
      • AuthResponse
      • Availability
      • CustomAvailability
      • Car
      • Customer
      • Booking
      • BookingUpdateRequest
      • BookingStatusUpdateConfig
      • Quote
      • ServiceHistory
      • ServiceReminder
      • WebhookRequest
      • ServiceCatalog

    Authorization

    Repairy API Authentication Guide#

    Welcome to the Repairy API, a secure and powerful way to integrate with our platform.
    Our API is designed with security and efficiency in mind, ensuring that only authorized partners can access protected resources. We use token-based authentication, which makes your experience safer, faster, and more reliable.
    With token authentication, you don’t need to send your credentials with every request. Instead, you receive an access token used to authenticate subsequent requests.

    What You Need Before You Start#

    Before you can start making API requests, you need to obtain authentication credentials from Repairy Support. These credentials act as your identification and are crucial for secure access.
    Unique application identifier
    Authentication key
    Partner identifier (required for every request)

    Header Requirement#

    Include the following header in every request:
    This lets us verify and trace requests to your integration.

    Why Use Token-Based Authentication?#

    Our API utilizes token-based authentication, a secure and efficient method to access protected resources without repeatedly sending sensitive credentials.

    Benefits of Token-Based Authentication:#

    Improved Security → No need to transmit credentials with every request.
    Faster Access → Authenticate once, then use the access token for multiple requests.
    Token Expiry → Access tokens have a defined lifespan, reducing security risks.
    Scalable & Lightweight → Works efficiently for high-performance applications.
    With token-based authentication, you get a seamless and secure API experience while maintaining full control over access and security.

    How Authentication Works#

    The authentication process is straightforward. Here’s how it works:

    Step 1: Request an Access Token#

    Before accessing protected API endpoints, your application needs to authenticate. This involves sending a request with your credentials.
    If the request is valid, the API will respond with:
    Access Token → Required for all authenticated API requests.
    Refresh Token → Allows you to renew the access token without logging in again.
    Access tokens expire after a certain period (48 hours). You must refresh them before they expire to maintain access.

    Step 2: Refreshing Your Access Token#

    To ensure uninterrupted access, you must renew your access token before it expires. Instead of logging in again, simply use the refresh token to get a new access token.
    Refresh tokens expire after a certain period (14 days).
    To refresh your token, send a request containing:
    Your current (valid) access token
    Your refresh token
    If the request is successful, a new access token is issued, keeping your session active without any disruptions.
    If your refresh token has expired, you must re-authenticate using your appKey and appSecret.
    Security Best Practices:
    Keep tokens private and secure. Never share them.
    Store tokens safely and use HTTPS to prevent unauthorized access.
    Regularly rotate your tokens to enhance security.

    Error Handling#

    When an API request fails, the response includes error details to help you identify and resolve the issue.

    Common Causes of Errors:#

    Missing or incorrect authentication credentials.
    Expired or invalid access tokens.
    Unauthorized access to restricted resources.
    By reviewing error responses, you can troubleshoot quickly and efficiently.

    API Endpoints#

    Access Token Request#

    Endpoint: Access Token API
    Purpose: Generates an initial access token using your credentials.

    Token Refresh#

    Endpoint: Refresh Token API
    Purpose: Renews your access token before expiration, ensuring uninterrupted access.

    Success Response#

    Successful requests return a consistent response format to simplify processing.

    Need Help?#

    Contact Repairy Support for assistance. Our team is here to ensure that your API integration is as smooth and hassle-free as possible.
    Modified at 2025-08-28 01:56:48
    Previous
    HTTP Headers
    Next
    Workshops
    Built with