eINVOICING
  1. Bearer Token Authentication
eINVOICING
  • eInvoicing Service
    • About Us
    • What We Offer
    • FAQ
    • Changelog
    • On Boarding
    • eInvoicing Service API
      • API Authentication
        • API Key Authentication
          • /Authentication/login
        • Bearer Token Authentication
          • Authentication Login Bearer Token
            POST
          • Authentication Refresh
            POST
      • API Endpoints
        • API Validations
        • Sending a Document
          • Sending a Document
          • Mandatory Fields' Descriptions B2C, B2B
          • Mobile Notifications
          • IAPR SIGN POLICY METHODS
          • QR OF THE DOCUMENT
          • Invoice/json
          • Invoice/credit
        • Purchase Orders for F&B
          • FnB Purchase Orders Documentation
          • Offline QR Code Implementation
          • Retrieve Open Order Documents (FnB)
        • Document Management
          • Retrieving a document
          • PDF Invoice Attachment
        • Alternative Currency Holding
          • ALTERNATIVE CURRENCY (AC)
        • Delivery Notes
          • Delivery Notes Documentation
          • /Invoice/cancelDeliveryNote
        • POS Integration
          • POS Integration
          • Offline QR Code Implementation
          • /PosSignatures/{issuerTin}
          • /Receipt
          • /PosTransactions/signpos
        • Delayed POS Payment
          • Delayed POS Payment
        • B2G Documents
          • B2G Documents
          • B2G Mandatory Fields
          • B2G Status response
          • B2G Soft Reject
          • RESEED INVOICE
          • ΕΓΚΥΚΛΙΟΣ ΠΡΟΣ ΠΑΡΟΧΟΥΣ-ΠΡΟΜΗΘΕΥΤΕΣ ΥΠΗΡΕΣΙΩΝ ΥΓΕΙΑΣ ΓΙΑ ΤΗΝ ΗΛΕΚΤΡΟΝΙΚΗ ΤΙΜΟΛΟΓΗΣΗ
          • BT-10 BuyerReference
          • /B2GInvoice/ReSeedInvoice
          • /B2GInvoice/GetLastStatus
      • JSON Structures & Payloads
        • EliseCoreDocument Structure
          • EliseCoreDocument Structure
        • Minimum & Conditional Fields
          • Minimum & Conditional Fields
        • Response Examples & Error Handling
          • Response Examples & Error Handling
      • Offline QR Code
        • Offline QR Code Instructions
      • Status MyData
        • MyData/status
      • Extra Functionalities
        • Archiver
          • Archiver Functionality
      • Terminology
        • Document Type Codes
        • VAT & TAX Codes
        • Country & Currency Codes
        • Measurement Unit Codes (IAPR & EN16931)
        • Self-Billing Remarks (IAPR)
        • Classification & Payment Method Codes (IAPR)
        • Special Invoice Category
      • VAT Validation
        • Greek VAT Check
        • EU VAT Check
      • Attachments
        • Attaching Media & PDFs
        • Invoice Document Upload (Invoice/File)
      • SOFTONE ERP Related Segments
        • SOFTONE Configurator
          • SOFTONE Configurator - B2G Mapping
    • eInvoicing Portal
      • Template Configuration (Default Template)
      • Single Sign-On (SSO)
        • Single Sign-on (SSO) Setup Instructions
        • Single Sign-On (SSO)
    • WIKI JSON Samples
      • 1.1 B2B
      • 1.3 B2B Sales Invoice Third Country
      • 5.2 B2B Credit Invoice Non-Associated
      • 2.1 B2B Service Rendered Invoice
      • 1.1 Debit B2G
      • 11.1 B2C Retail Sales Receipt
      • 11.4 Retail Sales Credit Note
  1. Bearer Token Authentication

Authentication Refresh

IMPACT DEMO API
https://einvoiceapiuat.impact.gr
IMPACT DEMO API
https://einvoiceapiuat.impact.gr
POST
https://einvoiceapiuat.impact.gr/Authentication/Refresh
Refresh POST request
💡
Endpoint: https://einvoiceapiuat.impact.gr/Authentication/refresh
Request Payload: “[token value from the refreshToken object]”
The response will be similar to the one received when issuing the access token. This request needs to be authenticated.
Insert your "accessToken" value in the "Authentication" param on the header of the POST call.
All requests to the API need to be authenticated by implementing JWT Bearer token authentication.
For example, to issue an invoice using the endpoint: https://einvoiceapiuat.impact.gr/invoice/json, the corresponding header would look like this:
Key: “Authorization”
Value: "Bearer <valid access token>" //(between Bearer and <valid access token> requires a space)
For proper functionality, please ensure the flow is implemented as follows:
Perform an initial login to obtain the access token.
The access token is valid for 15 minutes. After it expires (or shortly before), the refresh token endpoint should be called to obtain a new access token.
The refresh token is valid for 7 days and can be used for token renewal within that period.

Request

Header Params

Body Params application/json

Example
"Insert Token from Bearer login here"

Request Code Samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://einvoiceapiuat.impact.gr/Authentication/Refresh' \
--header 'Authorization: Insert Access Token from Bearer Login' \
--header 'Content-Type: application/json' \
--data-raw '"Insert Token from Bearer login here"'

Responses

🟢200Success
application/json
Body

Example
{
    "accessToken": "string",
    "refreshToken": {
        "token": "string",
        "expires": "string"
    }
}
🟠400Bad Request
Modified at 2025-07-23 14:50:47
Previous
Authentication Login Bearer Token
Next
API Validations
Built with