error E00003. invalid child element 'amount' in json.

[BlueTiger]

I just created a sandbox account and am just getting started with integrating authorize.net with our FileMaker database.

I'm getting the following error, but I'm pretty sure that 'amount' is supposed to be a child element of transactionRequest...

What am I doing wrong?

The element 'transactionRequest' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'amount' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'transactionType' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'.

{
	"createTransactionRequest" : 
	{
		"merchantAuthentication" : 
		{
			"name" : "4E8v4Wvu3",
			"transactionKey" : "6y77r45728BRYhwF"
		},
		"transactionRequest" : 
		{
			"amount" : "757.8",
			"billTo" : 
			{
				"address" : "400 Fairview Ave N",
				"city" : "Seattle",
				"company" : "Impinj Snacks",
				"firstName" : "",
				"lastName" : "",
				"state" : "WA",
				"zip" : "98109"
			},
			"order" : 
			{
				"invoiceNumber" : "ORDSEAGGAB10350"
			},
			"payment" : 
			{
				"creditCard" : 
				{
					"cardCode" : "999",
					"cardNumber" : "5424000000000015",
					"expirationDate" : "1220"
				}
			},
			"poNumber" : "",
			"tax" : "7.5",
			"transactionSettings" : 
			{
				"setting" : 
				{
					"settingName" : "testRequest",
					"settingValue" : "true"
				}
			},
			"transactionType" : "authCaptureTransaction"
		}
	}
}

[Aaron]

Hi @BlueTiger,

This should work if you just get the elements in the right order. Despite what you might think from seeing that we have a JSON interface, not everything about it works the same way as other JSON things you might have dealt with. One artifiact of the way it's implemented on our end is that order of elements matters.

The order in the API reference should be the correct one, so if you follow that and it still doesn't work, let us know.

[BlueTiger]

thanks for the reply.  

Unfortunately, FileMaker doesn't give me control over the order of the key-value pairs in the json it creates.  It always adds them in alphabetical order.

I guess I'm stuck using the XML api :(