Get next message

Service description

This service returns the oldest message not processed by customer. To set the messages as processed use in combination with Mark message as processedservice.

Use additional filters where needed.

Request

GET https://connect.lhv.com/messages/next

Headers

Name	Value	Description
Client-Code	customer value	For Service Providers only. Company registration code of the Service Provider or its customer. When using the Service Provider own value also related customers messages are returned by default - see also Filter-Service-Provider for more options.
Client-Country	customer value	For Service Providers only. Should match the value of Client-CodeA
Filter-Service-Provider	true / false or 1/0	Add this optional header to select service provider messages only when using Service Provider own value for Client-Code. Values: 1/true (filter is on) or 0/false (filter is off). This can be used by service providers to select only their own company messages in the queue. By default when Client-Code is the service provider itself, it returns the messages of all customers. Has no effect when Client-Code is not service provider.
Filter-Response-Type	CREDIT_DEBIT_NOTIFICATION, PAYMENT etc.	Add this optional header to filter specific service messages. The value can be any Message-Response-Type (e.g., ACCOUNT_STATEMENT, CREDIT_DEBIT_NOTIFICATION, PAYMENT). Using this parameter enables parallel processing of payment responses and debit-credit notifications separately. This allows immediate consumption of payment responses, even if there are thousands of pending notifications in the queue.

Body

-

Response

Headers

Name	Value	Description
Content-Type	application/xml or application/json	Format of the message body
X-Bank-Code	LHVUK, LHVEE	LHV Bank entity
Client-Code	customer value	When using service provider model - customer entity related to the message
Client-Country	customer value	When using service provider model - customer entity related to the message
Message-Request-Id	random string	Message-Request-Id from the the original request. There are cases where request id can be missing, for example the Debit Credit Notification.
Message-Response-Id	random string	Unique response id
Message-Response-Type	CREDIT_DEBIT_NOTIFICATION, PAYMENT etc.	Type of the response depending on the service.

Body

200 - next message

OK

Content depends on the service - see specifications of different services.

204 - no more messages

No content

403 - error

Error code and description

<Errors>
    <Error>
        <ErrorCode>FORBIDDEN</ErrorCode>
        <Description>User doesn't exist</Description>
    </Error>
</Errors>