# IRPCEvents.CreateEventCheckInRequest

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Vault API](https://developer.m-files.com/APIs/gRPC-API/vault/index.md) > [Events and notifications](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEvents/index.md)

HTML version: https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEvents/CreateEventCheckInRequest/

Badges: `Vault API / standard` `write` `session` `returns metadata structure version`

Asks the user who has an object checked out to check it in. Used by M-Files clients;
applications rarely call it.

- **Service:** [Events and notifications](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEvents/index.md) `MFiles.IRPCEvents`
- **gRPC method:** `/MFiles.IRPCEvents/CreateEventCheckInRequest`
- **HTTP (mf-http-grpc):** `POST /grpc/v1/create-event-check-in-request`
- **Request:** [`CreateEventCheckInRequestRequest`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEvents/CreateEventCheckInRequest/index.md#request)
- **Response:** [`CreateEventCheckInRequestResponse`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEvents/CreateEventCheckInRequest/index.md#response)
- **Book and level:** Vault API, standard
- **Kind:** write
- **Session:** Required: the session ID from LogIn in the mfiles-session-id-bin metadata.
- **Idempotent:** no
- **Returns metadata structure version:** yes (in the mfiles-metadata-version-bin trailer)
- **Streaming:** none (unary)

<a id="remarks"></a>

## Remarks

- Requires a vault session. No special vault rights are needed.
- The request goes to the user who has the latest version checked out. If the object is not
  checked out, or event logging is disabled in the vault, the call succeeds and does nothing.
- The recipient is notified by e-mail when notifications are enabled.

<a id="request"></a>

## Request: CreateEventCheckInRequestRequest

> Nested message fields are expanded to depth 3; follow a type link for deeper levels and for the type's own page.

| Field | Type | Description |
|---|---|---|
| `objid` | [`ObjID`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.ObjID/index.md) | The object that should be checked in. |
| `objid.type` | `int32` | The object type ID, for example 0 for documents. In a lookup value, the value list ID (for a lookup to objects, the object type ID). |
| `objid.item_id` | [`ItemID`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.ItemID/index.md) | The ID of the object within its type, in `item_id.internal_id`. |
| `objid.item_id.internal_id` | `int32` | The ID of the object or value list item. |
| `objid.item_id.external_repository_id` | [`ExternalRepositoryID`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.ExternalRepositoryID/index.md) | Used only for objects in external repositories (external connectors). Leave it unset for objects stored in the vault. |

<a id="response"></a>

## Response: CreateEventCheckInRequestResponse

No fields.