Can you provide a sample company to test annual report filing? We get the following validation error on trying to test this in the sandbox? {"errorMessage": "API backend third party service error.", "rootCause": "errors:[error:Annual Report Date cannot be before a previous Annual Report or the Founding Date.,..}
For filing the annual report, there is a discrepancy between the example request body and the directors schema in the documentation. Is the id property required for filing the change? If so, what should be the value passed to it?
{
...,
"directors": [
{
"officer": {
"email": "api.specs@api.specs",
"firstName": "firstName",
"id": 584282, // What should be the id?
"lastName": "lastName",
"partyType": "person",
"middleInitial": "",
"prevFirstName": "firstName",
"prevLastName": "lastName",
"prevMiddleInitial": ""
},
...]
}
In the Annual Return Schema, annualGeneralMeetingDateis not a required field. However, the latest announcement on Feb 04, 2025, lists mandatory changes. How do we validate these changes and send the right data points in the Annual Return filing?
* You will need to include information about your Annual General Meeting (AGM). There are three options to choose from:
* The date the AGM was held, or
* That the AGM will be held, or
* The date the AGM was waived or deemed to have been held
You can only submit filings for a business that is linked to the account an API key was created for.
The id property needs to match the id for the given director of your business. This can be determined using the GET /businesses/<business_identifer>/directors endpoint.
@achiu Thanks for your response. I have another question about the annual report schema. In the documentation it doesn’t have a description of the following fields from the Annual Report Request example provided here
@MKSi regarding your questions about the sample Annual Report Request containing fields not included in the schema, this is a mistake on our side. The id, isFeeAppied, isDirectorActionable and actions fields are not required. These fields are specific to the BC Registries applications and not applicable for Business API users. We will clean this up across our API specifications request examples.
The schema definitions have required fields marked in a lot of cases. This does not mean that this is the only validation that occurs. More complex validation often occurs in the Business API when a filing is submitted. As the schema definitions can be potentially used across different filings, we try to keep the schema definitions relatively simple in most cases to support different validation rules depending on the filing.
For the Annual Report filing, you should be able to test theannualGeneralMeetingDate validation by either submitting an Annual Report filing in the sandbox without the annualGeneralMeetingDate field or you can use the only_validate query parameter to test validation only for a draft filing.
Example API request URL for validating a draft filing
PUT {{business-api-sandbox-base-url}}/businesses/BC1234567/filings/<filing_id>?draft=true&only_validate=true
Just to clarify, in the case where the shareholders sign a resolution in lieu of an AGM, do we need to provide the date of the signature of the resolution in the Annual Return API call?