---
title: "Tick consent for home state"
method: POST
path: "/api/v1/teams/{teamId}/home/consent"
tags: ["Teams"]
---

# Tick consent for home state

`POST /api/v1/teams/{teamId}/home/consent`

Tick consent for fuse protection in the home state

## Path parameters

- `teamId` integer, required

## Request body

- ConsentRequest
  - `consent_type` 'FUSE_PROTECTION' | 'PEAK_PROTECTION', required

## Response `200`

OK

- MontaAppResponse — Standard response format for all Monta API endpoints
  - `status` 'CONTINUE' | 'SWITCHING_PROTOCOLS' | 'PROCESSING' | 'OK' | 'CREATED' | 'ACCEPTED' | 'NON_AUTHORITATIVE_INFORMATION' | 'NO_CONTENT' | 'RESET_CONTENT' | 'PARTIAL_CONTENT' | 'MULTI_STATUS' | 'ALREADY_IMPORTED' | 'IM_USED' | 'MULTIPLE_CHOICES' | 'MOVED_PERMANENTLY' | 'FOUND' | 'SEE_OTHER' | 'NOT_MODIFIED' | 'USE_PROXY' | 'SWITCH_PROXY' | 'TEMPORARY_REDIRECT' | 'PERMANENT_REDIRECT' | 'BAD_REQUEST' | 'UNAUTHORIZED' | 'PAYMENT_REQUIRED' | 'FORBIDDEN' | 'NOT_FOUND' | 'METHOD_NOT_ALLOWED' | 'NOT_ACCEPTABLE' | 'PROXY_AUTHENTICATION_REQUIRED' | 'REQUEST_TIMEOUT' | 'CONFLICT' | 'GONE' | 'LENGTH_REQUIRED' | 'PRECONDITION_FAILED' | 'REQUEST_ENTITY_TOO_LARGE' | 'REQUEST_URI_TOO_LONG' | 'UNSUPPORTED_MEDIA_TYPE' | 'REQUESTED_RANGE_NOT_SATISFIABLE' | 'EXPECTATION_FAILED' | 'I_AM_A_TEAPOT' | 'ENHANCE_YOUR_CALM' | 'UNPROCESSABLE_ENTITY' | 'LOCKED' | 'FAILED_DEPENDENCY' | 'UNORDERED_COLLECTION' | 'TOO_EARLY' | 'UPGRADE_REQUIRED' | 'PRECONDITION_REQUIRED' | 'TOO_MANY_REQUESTS' | 'REQUEST_HEADER_FIELDS_TOO_LARGE' | 'NO_RESPONSE' | 'BLOCKED_BY_WINDOWS_PARENTAL_CONTROLS' | 'UNAVAILABLE_FOR_LEGAL_REASONS' | 'REQUEST_HEADER_TOO_LARGE' | 'INTERNAL_SERVER_ERROR' | 'NOT_IMPLEMENTED' | 'BAD_GATEWAY' | 'SERVICE_UNAVAILABLE' | 'GATEWAY_TIMEOUT' | 'HTTP_VERSION_NOT_SUPPORTED' | 'VARIANT_ALSO_NEGOTIATES' | 'INSUFFICIENT_STORAGE' | 'LOOP_DETECTED' | 'BANDWIDTH_LIMIT_EXCEEDED' | 'NOT_EXTENDED' | 'NETWORK_AUTHENTICATION_REQUIRED' | 'CONNECTION_TIMED_OUT', required — HTTP status codes used in Monta API responses
  - `message` string, nullable — Primary response message for developers/logging
  - `origin` string, required — Name of the service that generated this response
  - `environment` string, required — Environment where this response was generated
  - `localizedMessage` string, nullable — User-friendly message that can be displayed to end users
  - `errorCode` string, nullable — Optional error code for categorizing errors
  - `context` object, nullable — Additional metadata related to the response
  - `errors` MontaAppResponseErrorDetail[], nullable — Detailed validation errors for form fields
    - `field` string, nullable — Name of the field that failed validation
    - `details` MontaAppResponseErrorDetailBody[], nullable — List of validation issues for the field
      - `message` string, required — Error message describing the validation issue
  - `statusCode` integer, required — Numeric HTTP status code

## Other responses

- `400` — The request is invalid
- `401` — Consumer with provided credentials was not found
- `403` — Operator doesn't have access to resource
- `404` — Entity with the provided id was not found

---

[API](https://skmtc.net/monta/apis/monta-partner-api.md) · [All operations](https://skmtc.net/monta/apis/monta-partner-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/monta/monta-partner-api/versions/517e18f11015/schema)