> For the complete documentation index, see [llms.txt](https://api2-ekycportal.innov8tif.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api2-ekycportal.innov8tif.com/emas-ekyc-portal/manual-verification/complete-journey-api.md).

# Complete Journey  API

## API Method

## To update the JourneyID's status as completed

<mark style="color:green;">`POST`</mark> `https://ekycportaldemo.innov8tif.com/api/ekyc/complete`

#### Request Body

| Name                                        | Type   | Description                          |
| ------------------------------------------- | ------ | ------------------------------------ |
| journeyID<mark style="color:red;">\*</mark> | string | Retrieve from 'Create JourneyID' API |

{% tabs %}
{% tab title="200: OK Successfully update the JourneyID's status as completed completed" %}
{% code title="Response Code Block" %}

```json
{
    "status": "success",
    "messageCode": null,
    "message": null,
    "completeDateTime": 1680775433552
}
```

{% endcode %}
{% endtab %}

{% tab title="400: Bad Request Failed to update the JourneyID's status" %}

```javascript
{
    "status": "error"
}
```

{% endtab %}

{% tab title="500: Internal Server Error Server Error" %}

```javascript
{
    "status": "Internal Server Error"
}
```

{% endtab %}
{% endtabs %}

### Input Example

{% code title="Request Code Block " %}

```json
{
    "journeyId":"584c7dfb-XXXX-XXXX-XXXX-b324ccaad308"
}

```

{% endcode %}

## Important Information

For Complete Journey API to work correctly, all enabled eKYC steps (i.e. OkayID, OkayDoc etc.) for the user must be completed first. Otherwise it will return an `INCOMPLETE_JOURNEY` error.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://api2-ekycportal.innov8tif.com/emas-ekyc-portal/manual-verification/complete-journey-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.