Reject Memo

curl -X POST https://api.companyflow.com/memos/550e8400-e29b-41d4-a716-446655440000/reject \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "comments": "Policy conflicts with existing HR guidelines. Please revise section 3."
  }'

const memoId = '550e8400-e29b-41d4-a716-446655440000';

const response = await fetch(
  `https://api.companyflow.com/memos/${memoId}/reject`,
  {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer YOUR_TOKEN',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      comments: 'Policy conflicts with existing HR guidelines. Please revise section 3.'
    })
  }
);

const data = await response.json();

import requests

memo_id = '550e8400-e29b-41d4-a716-446655440000'
url = f'https://api.companyflow.com/memos/{memo_id}/reject'
headers = {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json'
}
payload = {
    'comments': 'Policy conflicts with existing HR guidelines. Please revise section 3.'
}

response = requests.post(url, json=payload, headers=headers)
data = response.json()

{
  "success": true,
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "company_id": "123e4567-e89b-12d3-a456-426614174000",
    "created_by": "987e6543-e21b-12d3-a456-426614174000",
    "memo_type": "policy",
    "title": "Updated Remote Work Policy",
    "content": "Effective immediately, all employees are eligible for hybrid work arrangements...",
    "reference_number": "MEMO-2025-001",
    "priority": "high",
    "status": "rejected",
    "current_step": 1,
    "rejected_by": "abc12345-e89b-12d3-a456-426614174000",
    "rejected_at": "2025-03-03T15:30:00Z",
    "rejection_reason": "Policy conflicts with existing HR guidelines. Please revise section 3.",
    "created_at": "2025-03-03T10:00:00Z",
    "updated_at": "2025-03-03T15:30:00Z"
  }
}

{
  "success": false,
  "message": "invalid memo id"
}

{
  "success": false,
  "message": "you are not authorized to reject this memo at the current step"
}

{
  "success": false,
  "message": "unauthorized"
}

POST

memos

{id}

reject

curl -X POST https://api.companyflow.com/memos/550e8400-e29b-41d4-a716-446655440000/reject \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "comments": "Policy conflicts with existing HR guidelines. Please revise section 3."
  }'

const memoId = '550e8400-e29b-41d4-a716-446655440000';

const response = await fetch(
  `https://api.companyflow.com/memos/${memoId}/reject`,
  {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer YOUR_TOKEN',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      comments: 'Policy conflicts with existing HR guidelines. Please revise section 3.'
    })
  }
);

const data = await response.json();

import requests

memo_id = '550e8400-e29b-41d4-a716-446655440000'
url = f'https://api.companyflow.com/memos/{memo_id}/reject'
headers = {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json'
}
payload = {
    'comments': 'Policy conflicts with existing HR guidelines. Please revise section 3.'
}

response = requests.post(url, json=payload, headers=headers)
data = response.json()

{
  "success": true,
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "company_id": "123e4567-e89b-12d3-a456-426614174000",
    "created_by": "987e6543-e21b-12d3-a456-426614174000",
    "memo_type": "policy",
    "title": "Updated Remote Work Policy",
    "content": "Effective immediately, all employees are eligible for hybrid work arrangements...",
    "reference_number": "MEMO-2025-001",
    "priority": "high",
    "status": "rejected",
    "current_step": 1,
    "rejected_by": "abc12345-e89b-12d3-a456-426614174000",
    "rejected_at": "2025-03-03T15:30:00Z",
    "rejection_reason": "Policy conflicts with existing HR guidelines. Please revise section 3.",
    "created_at": "2025-03-03T10:00:00Z",
    "updated_at": "2025-03-03T15:30:00Z"
  }
}

{
  "success": false,
  "message": "invalid memo id"
}

{
  "success": false,
  "message": "you are not authorized to reject this memo at the current step"
}

{
  "success": false,
  "message": "unauthorized"
}

Reject a memo at its current workflow approval step. This stops the approval process and marks the memo as rejected, requiring the creator to either revise and resubmit or cancel the memo.

Authentication

Requires authentication with Bearer token. Available to:

Manager
HR Manager
Super Admin

Only users with approval authority at the current workflow step can reject the memo. Rejecting a memo is a significant action that stops the approval workflow.

Path Parameters

string

required

The unique identifier of the memo (UUID format)Example: "550e8400-e29b-41d4-a716-446655440000"

Request Body

string

Optional rejection comments explaining the reason for rejectionExample: "Policy conflicts with existing HR guidelines. Please revise section 3."

Response

boolean

Indicates if the request was successful

object

The updated memo object with rejected status

Show Memo properties

string

Unique identifier for the memo

string

UUID of the company

string

UUID of the employee who created the memo

string

Type of memo (e.g., “announcement”, “policy”, “notice”)

string

Memo title

string

Full memo content

string

Unique reference number for the memo

string

Priority level: “low”, “medium”, or “high”

string

Current status (will be “rejected” after this call)

integer

Workflow step where rejection occurred

string

UUID of the employee who rejected the memo

string

Rejection timestamp

string

Comments provided during rejection

string

ISO 8601 timestamp

string

ISO 8601 timestamp

curl -X POST https://api.companyflow.com/memos/550e8400-e29b-41d4-a716-446655440000/reject \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "comments": "Policy conflicts with existing HR guidelines. Please revise section 3."
  }'

const memoId = '550e8400-e29b-41d4-a716-446655440000';

const response = await fetch(
  `https://api.companyflow.com/memos/${memoId}/reject`,
  {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer YOUR_TOKEN',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      comments: 'Policy conflicts with existing HR guidelines. Please revise section 3.'
    })
  }
);

const data = await response.json();

import requests

memo_id = '550e8400-e29b-41d4-a716-446655440000'
url = f'https://api.companyflow.com/memos/{memo_id}/reject'
headers = {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json'
}
payload = {
    'comments': 'Policy conflicts with existing HR guidelines. Please revise section 3.'
}

response = requests.post(url, json=payload, headers=headers)
data = response.json()

{
  "success": true,
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "company_id": "123e4567-e89b-12d3-a456-426614174000",
    "created_by": "987e6543-e21b-12d3-a456-426614174000",
    "memo_type": "policy",
    "title": "Updated Remote Work Policy",
    "content": "Effective immediately, all employees are eligible for hybrid work arrangements...",
    "reference_number": "MEMO-2025-001",
    "priority": "high",
    "status": "rejected",
    "current_step": 1,
    "rejected_by": "abc12345-e89b-12d3-a456-426614174000",
    "rejected_at": "2025-03-03T15:30:00Z",
    "rejection_reason": "Policy conflicts with existing HR guidelines. Please revise section 3.",
    "created_at": "2025-03-03T10:00:00Z",
    "updated_at": "2025-03-03T15:30:00Z"
  }
}

{
  "success": false,
  "message": "invalid memo id"
}

{
  "success": false,
  "message": "you are not authorized to reject this memo at the current step"
}

{
  "success": false,
  "message": "unauthorized"
}

What Happens After Rejection

Workflow Stops

The memo approval workflow is immediately halted

Creator Notified

The memo creator receives a notification with rejection details and comments

Status Updated

Memo status changes to rejected and is no longer in the approval queue

Next Actions

The creator can revise the memo based on feedback and create a new version, or cancel the memo entirely

Best Practices

Providing helpful feedback:

Always include detailed comments explaining the reason for rejection
Reference specific sections or issues that need to be addressed
Suggest concrete improvements or alternatives
Be constructive to help the creator revise effectively

If the memo needs minor changes, consider communicating directly with the creator before rejecting. Rejection should be reserved for significant issues that require substantial revision.

Authorization Rules

Similar to approval, rejection requires:

The memo must be at a workflow step where you have approval authority
Managers can reject memos from their department or direct reports
HR Managers and Super Admins can reject any memo
The memo must be in pending status (not already approved or rejected)

Approve Memo - Approve a memo to move it forward
Get Memo - View memo details and status
List Memos - View memos with filtering
Mark as Read - Mark memo as read

Authentication

Companies

Employees

Departments

Designations

Levels

Roles & Permissions

Leave Types

Leave Requests

Leave Balances

Memos

Approvals

Authentication

Path Parameters

Request Body

Response

What Happens After Rejection

Best Practices

Authorization Rules

​Authentication

​Path Parameters

​Request Body

​Response

​What Happens After Rejection

​Best Practices

​Authorization Rules

​Related Endpoints

Authentication

Path Parameters

Request Body

Response

What Happens After Rejection

Best Practices

Authorization Rules

Related Endpoints