View on GitHub

easitrace

« Back to Contents

API | Troubleshooting Guide

This comprehensive guide helps you diagnose and resolve common issues with the EasiTrace movement services API. Refer to the error codes, service-specific solutions, and debugging checklist below.

Table of Contents

  1. Common Issues
  2. Service-Specific Issues
  3. Debugging Checklist
  4. FAQ
  5. Error Code Reference
  6. Support Contact Information

Common Issues

1. Authentication Failures (401, 403)

Issue: Invalid API Key

Error Messages:

Typical Response:

{
  "code": "A-1000",
  "description": "Service Credentials Invalid",
  "category": 9,
  "severity": 10,
  "field": "X-API-Key"
}

Causes:

Solutions:

  1. Verify API Key Header:
    • For Service Providers: Use X-ServiceProvider-API-Key header (preferred)
    • For Applications: Use X-Application-API-Key header (preferred)
    • Deprecated: X-API-Key header is no longer recommended
  2. Regenerate API Key:
    • Contact Rezare for Service Provider key regeneration
    • Service Providers can generate new Application keys via the API
    • Store new keys securely immediately after generation
  3. Verify Key Format:
    • Ensure the key is copied exactly without trailing spaces
    • Check that the key matches the current environment
    • Confirm the API key hasn’t been accidentally modified
  4. Check Service Provider Credentials:
    • Ensure Service Provider credentials are registered for the movement service
    • Verify property credentials are configured correctly
    • Use /api/service-providers/credentials endpoint to check

Example Request (Correct):

curl -X GET "https://api.easitrace.com/api/services" \
  -H "X-Application-API-Key: your-api-key-here" \
  -H "Content-Type: application/json"

Issue: Authorization Error (User Lacks Permissions)

Error Message:

Causes:

Solutions:

  1. Verify User Type:
    • Service Providers can access: /api/service-providers/… and /api/applications/…
    • Applications can access all other endpoints
  2. Use Correct Credentials:
    • Service Providers must use X-ServiceProvider-API-Key
    • Applications must use X-Application-API-Key
  3. Check Endpoint Access:
    • Service Provider endpoints require Service Provider authentication
    • Application-specific endpoints require Application authentication

Restricted Endpoints by Type:

Issue: Service Token Invalid or Expired

Error Code: A-1003 (Service Token Invalid or Expired)

Causes:

Solutions:

  1. Re-authenticate with Movement Service:
    • Call /api/service-providers/credentials to refresh credentials
    • Update Service Provider credentials if they’ve changed
  2. Check Service Provider Setup:
    • Verify Service Provider credentials are current
    • Confirm username/password for the movement service are correct
    • Some services (DAERA, RMIS) may require periodic re-authentication
  3. Implement Token Refresh Logic:
    • Cache tokens temporarily but implement refresh on token expiry
    • Handle token refresh as part of retry logic for failed transactions

2. Validation Errors (400)

Issue: Missing Required Parameters

Error Code: ES-1000 (Parameter Missing) HTTP Status: 400 Bad Request

Causes:

Common Missing Fields:

Solutions:

  1. Validate Request Structure: 
    {
  "reference": "unique-reference",
  "type": "MOV-ON",
  "speciesCode": "C",
  "propertyIdentifier": "20/002/0001",
  "transactionDate": "2024-01-15T10:30:00Z",
  "fields": {}
}
  2. Get Service-Specific Fields:
    • Call GET /api/services/{serviceId}/fields to get required fields
    • Check field required attribute
    • Include all fields marked as required
  3. Verify Data Types:
    • Ensure field types match specification
    • Dates should be ISO 8601 format
    • IDs should be valid UUIDs

Issue: Invalid Data Format

Error Code: MS-1004 (Invalid Format) or ES-1002 (Invalid Data) HTTP Status: 400 Bad Request

Typical Errors:

{
  "code": "MS-1004",
  "field": "Movement.DepartureDate",
  "description": "Invalid date format. Expected YYYY-MM-DD",
  "category": 2,
  "severity": 6
}

Common Format Issues:

Solutions:

  1. Date Formatting:
    • Use ISO 8601 format: 2024-01-15T10:30:00Z or 2024-01-15T10:30:00+00:00
    • For date-only fields: YYYY-MM-DD format
    • Verify timezone information if required by service
  2. Animal Identifiers:
    • RFID tags: Verify format per service (usually 12-15 digits)
    • Visual tags: Check against service specification
    • Ensure tags are not duplicated within same transaction
  3. Property Identifiers:
    • BCMS/ScotMoves/ScotEID: CPH format (e.g., “20/002/0001”)
    • RMIS: GLN format
    • EIDCymru/LIS/NLIS: Service-specific format
    • NAIT: 7-digit format
    • Confirm format matches property’s movement service
  4. Field Validation:
    • Call /api/services/{serviceId}/fields endpoint
    • Review field definition including format and constraints
    • Test with sample data before production use

Issue: Invalid Data Value

Error Code: MS-1005 (Invalid Data Value) HTTP Status: 400 Bad Request

Causes:

Common Value Errors:

{
  "code": "MS-1005",
  "field": "Animal.BirthDate",
  "description": "Birth date cannot be in the future",
  "category": 1,
  "severity": 6
}

Solutions:

  1. Date Validation:
    • Birth dates must be in the past
    • Transaction dates must be reasonable (not years in the past/future)
    • Arrival date must be after departure date
  2. Animal Count Validation:
    • expectedCount must match actual animal count
    • Head count must be positive integer
    • Ensure consistency between animals list and count
  3. Property Validation:
    • Verify property exists for the application
    • Property must support the species
    • Property must be registered with the movement service
    • Confirm property identifier format for the service
  4. Species Compatibility:
    • Check service capabilities for species
    • Some services only support specific animals
    • NAIT (New Zealand): Only cattle and deer
    • NLIS (Australia): Only cattle and sheep

3. Timeout Errors (408, 504)

Issue: Request Timeout (408)

HTTP Status: 408 Request Timeout

Causes:

Solutions:

  1. Check Network Connectivity: 
    # Verify API endpoint accessibility
curl -I https://api.easitrace.com/api/services
  2. Implement Retry Logic:
    • Retry with exponential backoff
    • Maximum 3-5 retries recommended
    • Wait 1, 2, 4 seconds between retries
  3. Increase Timeout Values:
    • Default HTTP timeout: 30 seconds
    • For large batches: increase to 60 seconds
    • For complex validations: increase to 90 seconds
  4. Reduce Payload Size:
    • Submit transactions individually instead of batches
    • Limit animals per transaction to 50-100
    • Split large requests into smaller chunks

Issue: Bad Gateway / Service Unavailable (504)

HTTP Status: 504 Gateway Timeout or 503 Service Unavailable

Causes:

Solutions:

  1. Check Service Status:
    • Verify movement service is online
    • Check EasiTrace status page for maintenance notices
    • Some services have maintenance windows (schedule varies)
  2. Implement Retry with Backoff: 
    // Exponential backoff retry pattern
var maxRetries = 5;
var delay = TimeSpan.FromSeconds(1);
   
for (int i = 0; i < maxRetries; i++)
{
    try
    {
        // Make API call
        return await client.PostAsync(url, content);
    }
    catch (HttpRequestException) when (i < maxRetries - 1)
    {
        await Task.Delay(delay);
        delay = TimeSpan.FromSeconds(delay.TotalSeconds * 2);
    }
}
  3. Queue Failed Transactions:
    • Store failed transactions locally
    • Retry periodically (every 5 minutes, 15 minutes, etc.)
    • Monitor retry queue for stuck messages
  4. Contact Support:
    • If 503 errors persist for >30 minutes
    • Verify your service credentials are correct
    • Check if your IP has been blocked

4. Service Unavailable (503)

HTTP Status: 503 Service Unavailable Error Code: MS-1007 (Service System Error) or MS-1008 (Service System Error - Retry)

Causes:

Solutions:

  1. Check Error Category:
    • Category 5 (Service System Error): Retry required
    • Category 6 (Service System Error - Retry): Specific retry required
  2. Implement Automatic Retry:
    • Wait 5-10 seconds before first retry
    • Use exponential backoff for subsequent retries
    • Maximum wait time: 5 minutes between retries
  3. Monitor Service Health:
    • Poll /api/health endpoint if available
    • Check movement service status pages
    • Subscribe to status update notifications
  4. Graceful Degradation:
    • Queue transactions locally if service is down
    • Provide user feedback about temporary unavailability
    • Implement fallback UI for offline scenarios

5. Transaction Processing Errors

Issue: Duplicate Transaction / Duplicate Animal

Error Code: MS-1003 (Duplicate Animal) or AN-1000 (Duplicate) HTTP Status: 400 Bad Request

Causes:

Solutions:

  1. Implement Idempotency: 
    {
  "reference": "unique-transaction-id-2024-01-15-001",
  "type": "MOV-ON"
}
    • Use unique reference per transaction
    • Retry with same reference (will be identified as duplicate safely)
  2. Check Animal Existence:
    • Query animal before attempting registration
    • Use GET-ANM capability to list property animals
    • Verify animal is not already tagged
  3. Handle Duplicate Gracefully:
    • Catch duplicate error
    • Verify the existing animal matches expectations
    • Update animal record if needed using retag capability (RMIS)

Issue: Unknown Animal

Error Code: MS-1010 (Unknown Animal)

Causes:

Solutions:

  1. Verify Animal Identity: 
    {
  "capability": "GET-ANM",
  "propertyIdentifier": "20/002/0001"
}
    • Query animals at source property using GET-ANM
    • Confirm animal exists with correct tag
  2. Check Animal Status:
    • Verify animal is still registered at the property
    • Confirm animal hasn’t been previously moved off
    • Check if animal is in isolation/quarantine
  3. Handle Missing Animals:
    • For movements: Use untagged animals with head count instead
    • For registrations: Create new animal record with REG transaction
    • For retag: First move animal to property if missing

Issue: Condition Violation

Error Code: MS-1002 (Condition Violation) Category: 4 (Condition Violation)

Causes:

Solutions:

  1. Verify Business Rules:
    • Check minimum age requirements
    • Verify animal health status
    • Confirm no conflicting movements exist
    • Validate dates are sequential
  2. Review Movement History:
    • Query recent movements for the animal
    • Check for pending movements
    • Verify no duplicate confirmations needed
  3. Contact Support if Rule is Blocking:
    • Some rules may have exceptions
    • Business rule interpretations may vary by region
    • Support may be able to provide guidance

Issue: Transaction Not Allowed

Error Code: MS-1009 (Transaction Not Allowed) Category: 7 (Transaction not Allowed) Severity: 10 (Fatal)

Causes:

Solutions:

  1. Verify Service Capabilities: 
    # Get service capabilities
GET /api/services/{serviceId}/capabilities
    • Confirm transaction type is supported
    • Check if property supports the capability
    • Verify species is supported
  2. Check Service Mapping:
    • Reference /docs/service-selection.md for service availability
    • Different countries/regions use different services
    • Species support varies by service and location
  3. Review Property Configuration:
    • Verify property is registered with the service
    • Check property supports the species
    • Confirm no restrictions are in place

Service-Specific Issues

BCMS

Service ID: 6a341eb4-828a-472f-afef-5566671738a0
Service Tag: BCMS
Country: England
Species: Cattle
Property Format: CPH (County/Parish/Holding)

Common BCMS Errors

Error Code Field Cause Solution
MS-1005 Departure.Identifier Invalid CPH format Use format: XX/XXX/XXXX (e.g., 20/002/0001)
MS-1002 Animal.Age Animal too young to move Cattle must be >= 6 weeks old
MS-1003 Animal.RFID Duplicate tag at property Check property animals first using GET-ANM
MS-1010 Animal.RFID Animal not found at source Verify animal exists at departure property
MS-1004 Movement.Date Invalid date format Use YYYY-MM-DD format

BCMS-Specific Validation Rules

Cattle Movement Requirements:

Dead Animal Recording:

Birth Registration:

BCMS Retry Strategy

Contact: BCMS support for CPH validation issues

ScotMoves

Service ID: 8f34d5c2-91e8-4f2a-bb3c-7d8c9e4f5a6b
Service Tag: SCOTMOVES
Country: Scotland
Species: Cattle, Sheep
Property Format: CPH (County/Parish/Holding)

Common ScotMoves Errors

Error Code Field Cause Solution
MS-1005 Destination.Identifier Invalid destination CPH Use 10-digit CPH format
MS-1002 Movement.ConfirmationNo Duplicate confirmation Only one transaction per confirmation
A-1000 ServiceProviderAuth Invalid credentials Contact ScotMoves support, update credentials
MS-1006 Movement Malformed request Verify all required fields present
MS-1007 Any Service system error Retry after 30 seconds

ScotMoves-Specific Validation Rules

Common Settings for Cattle and Sheep:

Authentication Notes:

ScotMoves Retry Strategy

Contact: ScotMoves technical support for credential issues

RMIS

Service ID: c8e4b2a1-5f7c-4d9e-8a2b-6f1c3e4d5f6g
Service Tag: RMIS
Country: South Africa
Species: Cattle, Sheep, Goats, Pigs
Property Format: GLN (Global Location Number)

Common RMIS Errors

Error Code Field Cause Solution
MS-1005 GLN.Format Invalid GLN format Use 13-digit GLN (e.g., 6123456789001)
A-1000 RMIS.Credentials Invalid username/password Regenerate credentials in RMIS portal
MS-1002 Movement.Rules Violation of movement rules Check minimum holding period (varies by region)
MS-1010 Animal.Tag Animal not in RMIS system Register animal first using REG capability
MS-1004 Animal.Breed Invalid breed code Use RMIS-approved breed codes

RMIS-Specific Validation Rules

Movement Requirements:

Retag Capability (RET):

Update Movement Capability:

Breed Codes:

RMIS Retry Strategy

Special Handling: RMIS has stricter validation than other services. Always validate locally before submission.

Contact: RMIS support for business rule clarification

DAERA/NIFAIS

Service ID: d4f5e6a7-2c3d-4e5f-6a7b-8c9d0e1f2a3b
Service Tag: DAERA
Country: Northern Ireland
Species: Cattle, Pigs
Property Format: Farm Identifier

Common DAERA Errors

Error Code Field Cause Solution
A-1001 User.Credentials Invalid farm login Verify DAERA portal credentials
MS-1004 Farm.Number Invalid farm number Confirm farm registration in DAERA
MS-1005 Animal.Age Movement restrictions for age Young cattle may have movement restrictions
MS-1007 Any DAERA system unavailable Usually resolves within 30 minutes
MS-1002 Passport Passport requirements not met Cattle may need passport for some movements

DAERA-Specific Validation Rules

Authentication Specifics:

Cattle Movement:

Farm Requirements:

DAERA Authentication Issues

Issue: “User Credentials Invalid”

Issue: “Service System Error” from DAERA

DAERA Retry Strategy

Contact: DAERA NIFAIS support (Northern Ireland specific)

ARAMS

Service ID: e5g6f7h8-3d4e-5f6g-7h8i-9j0k1l2m3n4o
Service Tag: ARAMS-ABATTOIR or ARAMS-FARM
Country: Australia
Species: Cattle, Sheep, Pigs, Goats
Property Format: Abattoir/Farm Identifier

Common ARAMS Errors

Error Code Field Cause Solution
MS-1005 Abattoir.Code Invalid abattoir code Verify with ARAMS-approved abattoirs
A-1000 ARAMS.Credentials Invalid facility credentials Update credentials for abattoir/farm
MS-1002 Livestock.Age Age restrictions for transport Check ARAMS age requirements
MS-1010 Animal.PIC Animal not in NLIS Verify animal is registered in NLIS first
MS-1004 Transaction Malformed request Review ARAMS field requirements

ARAMS-Specific Validation Rules

Two Service Tags:

Livestock Requirements:

Abattoir Submissions:

ARAMS Retry Strategy

Note: ARAMS integration is commonly problematic. Always verify NLIS integration first.

Contact: ARAMS support for abattoir code verification

LIS

Service ID: f6h7i8j9-4e5f-6g7h-8i9j-0k1l2m3n4o5p
Service Tag: LIS
Country: England
Species: Sheep
Property Format: CPH (County/Parish/Holding)

Common LIS Errors

Error Code Field Cause Solution
MS-1005 CPH.Format Invalid CPH format Use 10-digit format: XX/XXX/XXXX
MS-1004 Eartag.Format Invalid eartag format Eartag should be numeric, 6 digits
MS-1010 Sheep.ID Sheep not registered at farm Check property animals with GET-ANM
MS-1002 Movement.Date Date conflict with existing records Cannot move sheep twice on same day
A-1000 LIS.Credentials Invalid LIS login Update credentials for LIS system

LIS-Specific Validation Rules

Sheep Movement:

LIS Authentication:

Annual Requirements:

LIS Retry Strategy

Contact: LIS support for flock-specific issues

EIDCymru

Service ID: g7i8j9k0-5f6g-7h8i-9j0k-1l2m3n4o5p6q
Service Tag: EIDCYMRU
Country: Wales
Species: Sheep, Cattle, Goats, Deer
Property Format: CPH (County/Parish/Holding)

Common EIDCymru Errors

Error Code Field Cause Solution
MS-1005 CPH.Format Invalid CPH format Use 10-digit CPH (XX/XXX/XXXX)
MS-1004 Tag.Format Invalid tag format Format varies by species
A-1000 EIDCymru.Creds Invalid credentials Update in EIDCymru portal
MS-1010 Animal Animal not in EIDCymru Register first or check property
MS-1007 System EIDCymru unavailable Retry after 30 seconds

EIDCymru-Specific Validation Rules

Multi-Species Support:

CPH Requirements:

Language Support:

EIDCymru Retry Strategy

Contact: EIDCymru support for Welsh-specific guidance

NLIS

Service ID: h8j9k0l1-6g7h-8i9j-0k1l-2m3n4o5p6q7r
Service Tag: NLIS
Country: Australia
Species: Cattle, Sheep
Property Format: PIC (Property Identification Code)

Common NLIS Errors

Error Code Field Cause Solution
MS-1005 PIC.Format Invalid PIC format PIC must be 7-8 characters
MS-1010 Animal.Tag Animal not in NLIS Verify animal registered in state scheme
A-1000 NLIS.Credentials Invalid credentials Update in NLIS portal
MS-1002 Movement.Date Date outside acceptable range Movement must be current/recent
MS-1004 Tag.Format Invalid tag format Cattle 10 digits, sheep 6 digits

NLIS-Specific Validation Rules

Animal Identification:

Property Identification:

National Traceability:

NLIS Retry Strategy

State-Specific Issues:

Contact: NLIS support (state-specific) or AAFCO for national issues

NAIT

Service ID: i9k0l1m2-7h8i-9j0k-1l2m-3n4o5p6q7r8s
Service Tag: NAIT
Country: New Zealand
Species: Cattle, Deer
Property Format: NAIT Location Identifier

Common NAIT Errors

Error Code Field Cause Solution
MS-1005 Location.ID Invalid location ID NAIT location must be 6-7 digits
MS-1004 Animal.Tag Invalid NAIT tag format NAIT tags are numeric, 10+ digits
A-1000 NAIT.Credentials Invalid credentials Update in NAIT online portal
MS-1010 Animal Animal not in NAIT Register in NAIT before movement
MS-1007 System NAIT service error Retry after 30 seconds

NAIT-Specific Validation Rules

Location Identifiers:

Animal Identification:

Movement Requirements:

Cattle and Deer:

NAIT Retry Strategy

Note: NAIT is highly regulated. Consult official NAIT documentation for business rules.

Contact: NAIT (New Zealand Ministry for Primary Industries)

ScotEID

Service ID: j0l1m2n3-8i9j-0k1l-2m3n-4o5p6q7r8s9t
Service Tag: SCOTEID
Country: Scotland
Species: Sheep, Pigs
Property Format: CPH (County/Parish/Holding)

Common ScotEID Errors

Error Code Field Cause Solution
MS-1005 CPH.Format Invalid CPH Use 10-digit format: XX/XXX/XXXX
MS-1004 Tag.Format Invalid eartag format Sheep: 6 digits; Pigs: 9 digits
A-1000 ScotEID.Creds Invalid credentials Update in ScotEID system
MS-1010 Animal Not registered in ScotEID Register in ScotEID first
MS-1002 Movement Violates ScotEID rules Check traceability requirements

ScotEID-Specific Validation Rules

Species-Specific Rules:

CPH Registration:

Traceability:

ScotEID Retry Strategy

Contact: ScotEID support for Scottish farming-specific issues

Debugging Checklist

Use this checklist to systematically diagnose issues:

Pre-Submission Checklist

Request Validation

Service Configuration

Transaction-Specific

Error Response Handling

Retry Logic

Monitoring

FAQ

Q1: What is the difference between a validation error and a service system error?

A: Validation errors (ES-*, MS-1004, MS-1005) indicate that your request data is invalid. These should not be retried; instead, fix the data and resubmit. Service system errors (MS-1007, MS-1008) indicate that the movement service is having technical difficulties. These should be retried with exponential backoff.

Q2: My API key is working for some endpoints but not others. Why?

A: Different API keys have different scopes:

Q3: How long should I wait before retrying a failed request?

A: Use exponential backoff:

Q4: Should I retry validation errors (400)?

A: No. Validation errors indicate that your request data is invalid. Retrying will fail in the same way. Instead:

  1. Analyze the error message
  2. Fix the identified issue
  3. Resubmit with corrected data

Q5: How do I know if a property is registered with a movement service?

A: Check property configuration:

  1. Call GET /api/properties/{propertyId} to get property details
  2. Review the services array in the response
  3. Verify the movement service tag is listed
  4. Confirm credentials are configured (check /api/properties/{propertyId}/credentials)

Q6: What is the maximum number of animals I can submit in one transaction?

A: This varies by service:

If you exceed the limit, split into multiple transactions.

Q7: Why is my movement being rejected with a “Condition Violation” error?

A: Common reasons:

Review the service-specific rules for your species and movement type.

Q8: How do I handle duplicate transactions if idempotency isn’t guaranteed?

A: Implement the following pattern:

// 1. Submit transaction with unique reference
var reference = $"TXN-{DateTime.Now:yyyyMMdd-HHmmss}-{Guid.NewGuid().ToString().Substring(0, 8)}";

// 2. Store reference and response locally
var response = await client.SubmitTransaction(transaction);
LogTransaction(reference, response);

// 3. On retry with same reference, check if already submitted
var existing = FindTransactionByReference(reference);
if (existing != null && IsSuccessful(existing))
{
    // Already submitted successfully
    return existing;
}

// 4. Otherwise, retry submission

Q9: What should I do if the movement service is unavailable?

A: Implement a queue:

// 1. Catch service unavailable errors (503, 504)
// 2. Store transaction in local queue (database, file, or message queue)
// 3. Implement background job to retry periodically
// 4. Monitor queue for stuck messages (>24 hours old)
// 5. Alert admin if queue grows too large
// 6. Provide UI feedback to user about delayed submission

Q10: How do I know if my credentials are wrong vs. the service is down?

A: Check error codes:

To debug credentials specifically:

  1. Test credentials directly in the movement service portal
  2. Verify credentials are correctly formatted
  3. Check if credentials need to be refreshed (password expiration)
  4. Ensure credentials are stored without spaces or encoding issues

Q11: What fields are actually required for my transaction?

A: Call the service fields endpoint:

GET /api/services/{serviceId}/fields

Response includes:

{
  "fields": [
    {
      "key": "Movement.DepartureDate",
      "name": "Departure Date",
      "required": true,
      "type": "date",
      "format": "YYYY-MM-DD"
    }
  ]
}

Review the required attribute for each field.

Q12: How do I debug issues with specific animals in a transaction?

A: Use the animal-specific error fields:

{
  "code": "MS-1010",
  "field": "Animals[0].RFID",
  "description": "Animal with RFID '111222333' not found at property"
}

The array index in field shows which animal (0-based) has the issue. Query the animal:

GET /api/transactions/{transactionId}/animals/{index}

Error Code Reference

EasiTrace Errors (ES-*)

Code Category Severity Meaning Retriable
ES-1000 Invalid Request Severe Parameter Missing No
ES-404 Invalid Request Low Not Found No
ES-1001 Invalid Request Low Already Exists No
ES-1002 Invalid Data Medium Invalid Data No
ES-1003 Invalid Request Medium Invalid Request No
ES-1004 Invalid Request Low Service Not Found No
ES-1005 Invalid Request Low Species Not Supported No
ES-1006 Invalid Request Low Capability Not Supported No
ES-1007 Service Error Fatal Server Error Yes

Movement Service Errors (MS-*)

Code Category Severity Meaning Retriable
MS-1000 Service Error High Unknown Error Yes
MS-1001 Authentication High Authentication Error No
MS-1002 Condition Violation High Condition Violation No
MS-1003 Animal Medium Duplicate Animal No
MS-1004 Invalid Format High Invalid Format No
MS-1005 Invalid Data High Invalid Data Value No
MS-1006 Invalid Request Fatal Invalid Request No
MS-1007 Service Error Fatal Service System Error Yes
MS-1008 Service Error (Retry) Medium Service System Error - Retry Yes
MS-1009 Transaction Not Allowed Fatal Transaction Not Allowed No
MS-1010 Animal High Unknown Animal No
MS-1012 Information Low Information Message No

Authentication Errors (A-*)

Code Category Severity Meaning Retriable
A-1000 Authentication Fatal Service Credentials Invalid No
A-1001 Authentication Fatal User Service Credentials Invalid No
A-1002 Authentication High Authorisation Error No
A-1003 Authentication High Service Token Invalid No

Animal Errors (AN-*)

Code Category Severity Meaning Retriable
AN-1000 Animal Severe Duplicate Animal No
AN-1001 Animal Severe Unknown Animal No

HTTP Status Code Mapping

Status Meaning Retriable Typical Codes
400 Bad Request No ES-1000, MS-1004, MS-1005
401 Unauthorized No A-1000, A-1001
403 Forbidden No A-1002
404 Not Found No ES-404
408 Request Timeout Yes (timeout on network)
500 Internal Server Error Yes ES-1007
503 Service Unavailable Yes MS-1007, MS-1008
504 Gateway Timeout Yes (service timeout)

Support Contact Information

EasiTrace Support

Email: support@easitrace.com
Phone: +44 (0) 1234 567890
Hours: Monday-Friday, 9 AM - 5 PM GMT
Response Time: 4 hours for critical issues, 24 hours for standard

For Issues:

Service-Specific Support Contacts

BCMS (England)

Website: https://www.gov.uk/guidance/apply-to-give-cattle-movement-notice-bcms
Email: bcms@example.gov.uk
Phone: +44 (0) 8000 201 602
Support Hours: Monday-Friday, 8 AM - 5 PM GMT

For Issues:

ScotMoves (Scotland)

Website: https://www.ruralpayments.org/public/scot-moves/
Email: scottish-cattle@example.gov.uk
Phone: +44 (0) 300 244 4000
Support Hours: Monday-Friday, 8 AM - 5 PM GMT

For Issues:

RMIS (South Africa)

Website: https://www.rmis.co.za/
Email: support@rmis.co.za
Phone: +27 (0) 12 000 1234
Support Hours: Monday-Friday, 8 AM - 5 PM SAST

For Issues:

DAERA/NIFAIS (Northern Ireland)

Website: https://www.daera-ni.gov.uk/articles/nifais-livestock-information-system
Email: nifais@daera.gov.uk
Phone: +44 (0) 300 200 7846
Support Hours: Monday-Friday, 8:30 AM - 5 PM GMT

For Issues:

ARAMS (Australia)

Website: https://www.arams.com.au/
Email: support@arams.com.au
Phone: +61 (0) 2 1234 5678
Support Hours: Monday-Friday, 8 AM - 5 PM AEST

For Issues:

LIS (England - Sheep)

Website: https://www.gov.uk/guidance/animal-movements-and-testing-for-sheep-keepers
Email: lis@example.gov.uk
Phone: +44 (0) 8000 201 602
Support Hours: Monday-Friday, 8 AM - 5 PM GMT

For Issues:

EIDCymru (Wales)

Website: https://gov.wales/animal-health-and-welfare
Email: EIDCymru@example.gov.uk
Phone: +44 (0) 300 062 5015
Support Hours: Monday-Friday, 8 AM - 5 PM GMT (also Welsh language support)

For Issues:

NLIS (Australia - National)

Website: https://www.animalhealthaustralia.com.au/nlis/
Email: nlis@animalhealthaustralia.com.au
Phone: +61 (0) 2 6232 5522
Support Hours: Monday-Friday, 8 AM - 5 PM AEST

For Issues:

NAIT (New Zealand)

Website: https://www.mpi.govt.nz/nait/
Email: nait@mpi.govt.nz
Phone: +64 (0) 800 00 8287
Support Hours: Monday-Friday, 8 AM - 5 PM NZST

For Issues:

ScotEID (Scotland - Sheep/Pigs)

Website: https://www.ruralpayments.org/public/scoteid/
Email: scoteid@example.gov.uk
Phone: +44 (0) 300 244 4000
Support Hours: Monday-Friday, 8 AM - 5 PM GMT

For Issues:

When to Contact Support

Contact EasiTrace support for:

Contact Movement Service support for:

Provide to Support:

Additional Resources

Last Updated: January 2024
Document Version: 1.0
Maintained By: EasiTrace Technical Documentation Team